agent-desktop-macos — Claude Code skill: what it does, how to install
agent-desktop-macos — a skill for Claude Code that guides desktop automation on macOS using the agent-desktop CLI. Directs permission workflows and controls menus, system surfaces, and notifications.
Apache-2.0 1,100 installs ★ 25,974 updated 2026-11-15
npx skills add vercel-labs/agent-desktop --skill agent-desktop-macos -a claude-codeWhat agent-desktop-macos does
This skill provides platform rules for driving macOS user interfaces through the agent-desktop CLI. It instructs the agent on dispatching physical clicks, text typing, and scrolling, while keeping native menu clicks mapped to AXPress. It also covers inspecting the Dock, Notification Center banners, and status icons via --surface menu-bar-extras.
It handles macOS security permissions directly. When actions fail with permission errors, the agent runs agent-desktop permissions --guide to walk through Privacy & Security approvals. Actions like hover, drag, and double-click require the --headed flag.
Requires the agent-desktop CLI and macOS 13 or later on Intel or Apple Silicon hardware. Without Accessibility permissions enabled for the parent terminal, accessibility trees cannot be read.
What it helps with
- configure Accessibility and Screen Recording permissions using guided CLI steps
- interact with application menubars and system status extras
- target background processes and menu bar apps without standard windows
- dismiss notifications safely by verifying application name and title
Example prompts for the agent
- Check current TCC status with agent-desktop permissions
- Inspect the active app menu bar using agent-desktop snapshot --surface menubar
- Dismiss the incoming alert from Slack in Notification Center
How to install agent-desktop-macos
1Skills CLI (Vercel)
npx skills add vercel-labs/agent-desktop --skill agent-desktop-macos -a claude-code2Manually: put the files in place
~/.claude/skills/agent-desktop-macos/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/agent-desktop-macos/
1Skills CLI (Vercel)
npx skills add vercel-labs/agent-desktop --skill agent-desktop-macos -a codex2Manually: put the files in place
.agents/skills/agent-desktop-macos/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add vercel-labs/agent-desktop --skill agent-desktop-macos -a cursor2Manually: put the files in place
.cursor/skills/agent-desktop-macos/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install vercel-labs/agent-desktop skills/agent-desktop-macos2Manually: put the files in place
.github/skills/agent-desktop-macos/SKILL.md1Skills CLI (Vercel)
npx skills add vercel-labs/agent-desktop --skill agent-desktop-macos -a gemini-cli2Platform CLI
gemini skills install https://github.com/vercel-labs/agent-desktop --path skills/agent-desktop-macosManually: put the files in place
.devin/skills/agent-desktop-macos/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add vercel-labs/agent-desktop --skill agent-desktop-macos -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about agent-desktop-macos
How to install agent-desktop-macos in Claude Code?
Run npx skills add vercel-labs/agent-desktop --skill agent-desktop-macos -a claude-code. The skill file will be placed in ~/.claude/skills/agent-desktop-macos/SKILL.md.
What does agent-desktop-macos do?
It teaches the agent macOS-specific automation quirks for the agent-desktop CLI, covering TCC permissions, UI trees, and surface targeting.
What is required to run agent-desktop-macos?
You need macOS 13 or later, the agent-desktop CLI, and Accessibility access granted to the launching terminal application.
Source text
SKILL.md · Apache-2.0
--- name: agent-desktop-macos tags: macos-automation, accessibility, ax, tcc, ai-agent, gui-automation, cli requirements: - agent-desktop description: > macOS platform guide for the agent-desktop CLI. Use for desktop automation on macOS: granting Accessibility and Screen Recording permission (TCC), what headed mode does on macOS (physical-first click, type and scroll), surfaces (menu, menubar, sheet, popover, alert, dock, menu-bar-extras), menu bar apps and system panels with no window, Notification Center, Chromium and Electron apps including launch --cdp, and fixing PERM_DENIED, empty accessibility trees, ACTION_FAILED and APP_UNRESPONSIVE. --- # agent-desktop on macOS Read the core skill first (`agent-desktop skills get desktop`) for the observe, act, verify loop. This skill covers only what is different on macOS. When a command fails, find the symptom in [references/troubleshooting.md](references/troubleshooting.md). ## Requirements The sandbox provider on macOS is `macos`: a macOS VM that needs an Apple Silicon Mac, macOS 13 or later on the host and in the guest, and Xcode Command Line Tools. The first setup needs a person in the guest window; clones need none. See `agent-browser.dev/desktop/sandboxes/macos`. - macOS 13 or later, Intel or Apple Silicon. - Accessibility permission for the app that launches agent-desktop (Terminal, iTerm2, Warp, VS Code, Codex). macOS 27 and later name this list Device Control and Data Access. If System Settings lists the `agent-desktop` binary separately, grant it too. - Screen Recording permission, only for `screenshot` and for `session start --screenshots` artifacts. - Automation permission for System Events, only where a command reports it missing. ## First contact 1. Run `agent-desktop permissions`. 2. If a permission is denied, run `agent-desktop permissions --guide`. It opens the right System Settings page with a panel that shows the user which app to drag into the list. The user confirms with Touch ID or a password, and the panel moves to the next missing permission by itself. The command returns at once with `"guide": "started"`, `"already_running"` or `"not_needed"`. `agent-desktop permissions --request` shows the system prompts instead. 3. If the guide cannot run, open System Settings > Privacy & Security > Accessibility (Device Control and Data Access on macOS 27 and later). Add the launching app and turn it on. 4. Run `agent-desktop permissions` to confirm `granted`. The next agent-desktop call sees a new grant, so the launching app does not need a restart. Each command reads permissions in its own process, so a permission granted during a `batch` applies from the next CLI call, not to later items in that batch. 5. Run `agent-desktop snapshot -i` to confirm. It reads the focused app. `snapshot --app Finder -i` returns `WINDOW_NOT_FOUND` when Finder has no open window. `permissions` does not prompt. `permissions --request` can prompt, including for Automation. `permissions --guide` does not prompt and covers Accessibility and Screen Recording only. Automation reports `unknown` when macOS would need to prompt. ## What differs on macOS **Headed actions.** `click`, `right-click`, `type`, `clear` and `scroll` use physical paths first, except a click on an item in the application's native menu bar hierarchy, which calls `AXPress` without moving the pointer. A headless click on these menu items also calls `AXPress`. Process-owned refs have no window to focus; other ref-target pointer actions focus the exact owning window and verify the hit target before delivery. A headless `right-click` can use `AXShowMenu` when the target provides it. `expand`, `collapse`, `set-value`, `select`, `toggle`, `check`, `uncheck`, `focus` and `scroll-to` stay semantic under `--headed`. `double-click`, `triple-click`, `hover` and `drag` need `--headed`. Raw `--xy` input never changes focus. **Judge delivery by observation.** AX return codes do not prove an effect. Finder returns success from an `AXConfirm` that does nothing. Snapshot again or use `get` and `is` to check the result. **Surfaces.** Use `--surface menubar` for an app's File, Edit, and View menus. Use `--surface menu-bar-extras` for status items: with no `--app` it reads system items such as Wi-Fi, Battery, and Clock; with `--app` it reads that app's own item. Use `--surface dock` for the Dock. These shell surfaces are available headless through `open-system-surface`. A background app with no ordinary window, such as a menu-bar app or Control Center, can be observed through its process with `snapshot --app "Control Center"`. This applies to `window`, `menubar`, and `menu-bar-extras`, not `focused`; a regular app that has not shown its window returns `WINDOW_NOT_FOUND`. While a menu, sheet, alert, or popover is open, refs from the window tree behind it are the wrong target. **Menus.** `right-click` headless uses `AXShowMenu`. If the menu opened but the app returned `APP_UNRESPONSIVE` with `retry: unsafe`, do not retry. Inspect the menu with `--surface menu`. `menu` requires an open menu: if `snapshot --surface menu` returns `surface_absent` with `complete: true`, snapshot `menubar` when it exists, click its item without `--headed`, then snapshot `--surface menu`. An absent `menubar` can mean the app exposes no menu bar. A missing `complete`, `complete: false`, timeout or incomplete read is unknown, not absent. For combo boxes and menu buttons, use `select @ref "Option"`. `select` needs a closed-to-open menu transition, so dismiss any open menu first. **Notification Center.** The notification commands drive Notification Center through accessibility, with the rules in the core `commands-system` reference. When agent-desktop opens the center, it closes it afterwards and restores the previous app focus. Pass both `--expected-app` and `--expected-title` on a single dismiss or action, because the stack shifts. Use `wait --notification --app "App"` for banners that vanish before you list them. **Chromium and Electron.** agent-desktop switches on the web accessibility of a Chromium renderer automatically when it needs it. For a dense running app, use `snapshot --skeleton -i --compact`, then drill with `--root @ref`. **Identity.** `launch` accepts a display name (`"System Settings"`) or a bundle ID (`com.apple.systempreferences`). Other commands take the display name through `--app`, or the bundle ID or executable name (`ControlCenter`) when no running app has that display name. Window IDs such as `w-4521` stay valid for the life of the window. Find them with `list-windows`. **Refs use native addresses when available.** A ref turns back into the exact element it was captured from, so identical twins, such as several identical `Delete` buttons, each act on their own row. If the element was removed or the app restarted, the ref is `STALE_REF`, `details.kind: retained_object_stale`, and it never falls back to a search for a look-alike. When an app yields no address for an element, that ref follows the cross-platform rule instead and must have been the only element in its window with its role, native id, name and description. Take a fresh snapshot after a list changes. **Keys.** The primary modifier is `cmd`: `press cmd+c`, `press cmd+s`. Quit shortcuts such as `cmd+q`, `cmd+shift+q`, `cmd+alt+esc`, `ctrl+cmd+q` and `cmd+shift+delete` return `POLICY_DENIED` unless you pass `--force`. To quit an app, use `close-app`. Punctuation keys work in combos, as the symbol (`,` `.` `/` `;` `'` `[` `]` `\` `-` `=` `` ` ``) or by name (`comma`, `period`, `slash`, `semicolon`, `quote`, `leftbracket`, `rightbracket`, `backslash`, `minus`, `equal`, `grave`). Each one is sent with the key that types it in the active keyboard layout, so `press cmd+,` opens Settings on ANSI and JIS keyboards alike. **Cursor overlay.** `cursor-overlay enable` draws the agent cursor in a click-through window. It never moves the OS pointer or activates an app. The macOS motion and image limits are in the core `commands-system` reference.
© vercel-labs · Apache-2.0 · vercel-labs/agent-desktop