permiso-accessibility-permissions
Permission dialog UI for macOS accessibility and privacy settings, replicating the Codex Computer Use guided permissions flow
What this skill does
# Permiso — macOS Permission Dialog Helper
> Skill by [ara.so](https://ara.so) — Daily 2026 Skills collection.
Permiso provides a polished permission dialog UI for macOS apps that guides users through enabling accessibility and privacy settings — replicating the guided flow seen in OpenAI's Codex Computer Use product.
## What It Does
- Presents an animated, guided overlay panel directing users to open System Settings and enable specific permissions (e.g. Accessibility)
- Mirrors the UX pattern from Codex Computer Use: an on-screen assistant that walks users through enabling access
- Handles the common friction point of macOS permission flows with a clear, app-integrated UI
## Installation
### Swift Package Manager
Add to your `Package.swift`:
```swift
dependencies: [
.package(url: "https://github.com/zats/permiso", branch: "main")
]
```
Or in Xcode: **File → Add Package Dependencies** → enter `https://github.com/zats/permiso`
Then add `Permiso` to your target's dependencies:
```swift
.target(
name: "YourApp",
dependencies: ["Permiso"]
)
```
## Core API
### Basic Usage
```swift
import Permiso
@MainActor
func showAccessibilityHelper() {
PermisoAssistant.shared.present(panel: .accessibility)
}
```
### Triggering on App Launch
```swift
import SwiftUI
import Permiso
@main
struct MyApp: App {
var body: some Scene {
WindowGroup {
ContentView()
.onAppear {
checkAndRequestAccessibility()
}
}
}
@MainActor
func checkAndRequestAccessibility() {
let trusted = AXIsProcessTrusted()
if !trusted {
PermisoAssistant.shared.present(panel: .accessibility)
}
}
}
```
### AppDelegate Pattern
```swift
import AppKit
import Permiso
class AppDelegate: NSObject, NSApplicationDelegate {
func applicationDidFinishLaunching(_ notification: Notification) {
requestAccessibilityIfNeeded()
}
@MainActor
func requestAccessibilityIfNeeded() {
guard !AXIsProcessTrusted() else { return }
PermisoAssistant.shared.present(panel: .accessibility)
}
}
```
## Common Patterns
### Check Permission Before Sensitive Actions
```swift
import Permiso
import ApplicationServices
@MainActor
func performAccessibilityAction() {
guard AXIsProcessTrusted() else {
PermisoAssistant.shared.present(panel: .accessibility)
return
}
// Proceed with accessibility-dependent work
doAccessibilityWork()
}
```
### Polling for Permission Grant
```swift
import Permiso
import ApplicationServices
import Combine
class PermissionMonitor: ObservableObject {
@Published var isAccessibilityGranted = false
private var timer: AnyCancellable?
@MainActor
func startMonitoring() {
if AXIsProcessTrusted() {
isAccessibilityGranted = true
return
}
PermisoAssistant.shared.present(panel: .accessibility)
timer = Timer.publish(every: 1.0, on: .main, in: .common)
.autoconnect()
.sink { [weak self] _ in
if AXIsProcessTrusted() {
self?.isAccessibilityGranted = true
self?.timer?.cancel()
}
}
}
}
```
### SwiftUI View Integration
```swift
import SwiftUI
import Permiso
struct SettingsView: View {
@State private var accessibilityGranted = AXIsProcessTrusted()
var body: some View {
VStack(spacing: 16) {
HStack {
Image(systemName: accessibilityGranted ? "checkmark.circle.fill" : "xmark.circle.fill")
.foregroundColor(accessibilityGranted ? .green : .red)
Text("Accessibility Access")
}
if !accessibilityGranted {
Button("Enable Accessibility Access") {
requestAccess()
}
.buttonStyle(.borderedProminent)
}
}
.padding()
.onReceive(Timer.publish(every: 2, on: .main, in: .common).autoconnect()) { _ in
accessibilityGranted = AXIsProcessTrusted()
}
}
@MainActor
func requestAccess() {
PermisoAssistant.shared.present(panel: .accessibility)
}
}
```
## Requirements
- **macOS**: The library targets macOS (version as specified by the package; check for macOS 13+ for best compatibility)
- **Swift**: Swift 5.9+
- **Main Actor**: `PermisoAssistant.shared.present(panel:)` must be called from the main thread / `@MainActor` context
## Entitlements / Info.plist
For accessibility usage, ensure your app's `Info.plist` includes a usage description (though macOS doesn't require this like iOS, it's good practice), and that your app is **not sandboxed** or has the correct entitlements if it needs to use accessibility APIs:
```xml
<!-- In your .entitlements file if needed -->
<key>com.apple.security.temporary-exception.apple-events</key>
<true/>
```
For apps that actually use accessibility features after permission is granted:
```swift
// Request trust prompt (system dialog) alongside Permiso's guided UI
let options = [kAXTrustedCheckOptionPrompt.takeRetainedValue(): true] as CFDictionary
AXIsProcessTrustedWithOptions(options)
```
## Troubleshooting
**Panel doesn't appear**
- Ensure you're calling from `@MainActor` / main thread
- Check that your app has a visible window; the panel attaches to the app's UI context
**`AXIsProcessTrusted()` returns false even after granting**
- macOS caches trust state; the app may need to be relaunched or the check polled with a timer (see polling pattern above)
- Some sandboxed apps require a full app restart after granting accessibility
**Build errors: `cannot find 'PermisoAssistant' in scope`**
- Confirm `import Permiso` is at the top of the file
- Confirm the package is added to the correct target in Xcode, not just the project
**Panel appears but dismisses immediately**
- Make sure you're not overriding the window or calling dismiss logic right after present
- Avoid calling present inside a `Task { }` that gets cancelled immediately
## Key Types Reference
| Type | Description |
|------|-------------|
| `PermisoAssistant` | Singleton entry point — use `.shared` |
| `PermisoAssistant.shared.present(panel:)` | Shows the guided permission dialog |
| `.accessibility` | Panel type for Accessibility settings |
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.