| name | interceptor-macos |
| description | Drive native macOS apps via interceptor macos *: AX trees, background click/type/keys/drag/scroll, occluded or minimized window capture, browser chrome, URL bars, OS dialogs, Apple Events, trusted OS input, monitor/replay, overlays, vision, speech, NLP, JSC host utilities, Electron app web-content control via interceptor macos cdp, and in-process app runtime control via interceptor macos runtime. Background-first by contract; only app activate and open --activate move focus. Use for native apps, named browser app routing, window control, cross-app work, and system UI. Not for content inside browser pages. |
| metadata | {"short-description":"Drive native macOS apps via the interceptor CLI; background-first"} |
Interceptor macOS
Agent-operator skill for the macOS surface of Interceptor. Use the interceptor macos * CLI to drive native macOS applications: AX trees, OS-level trusted input, capture / vision / speech / NLP / Apple Events, monitor-and-replay, overlays. Use interceptor macos cdp / interceptor macos cdp app for Electron app web contents, and interceptor macos runtime for in-process native app runtime control. For content inside a browser tab load interceptor-browser instead.
The macOS bridge is a Swift daemon launched as a LaunchAgent / .app bundle. Links Apple frameworks only (Accessibility, ScreenCaptureKit, AVFoundation, Speech, Vision, NaturalLanguage, OSLogStore, NSAppleScript, container runtime). No private APIs.
This installed skill is self-contained. Source checkouts also have AGENTS.md, but packaged users may only have the skill directory below /Library/Application Support/Interceptor/skills.
Installed extensions may add capabilities under interceptor macos <prefix> <cmd>. Each carries its own skill (interceptor-ext-<name>); this skill does not describe them. Run interceptor extensions list to see what is installed.
Fast Path
interceptor status
interceptor macos trust
interceptor macos open "Finder"
interceptor macos read
interceptor macos act e5
interceptor macos act e3 "hello"
Treat eN refs as short-lived. AX state can change between calls; re-read before acting.
The One Rule
Only two commands move focus: interceptor macos app activate <app> and interceptor macos open <app> --activate. Everything else is background-first by contract — open (without --activate), all input verbs, all reads, capture, AX, menu, intent dispatch, scroll, drag, vision, overlays. If you call any other command and the user's frontmost app changes, that is a bug — file it.
Full contract + verb inventory + worked examples + pitfalls: references/background-first.md.
Workflows
Each workflow is a complete self-contained "you are doing X" procedure. Open the file when the task matches.
References
| File | Topic |
|---|
references/background-first.md | Full Background-First contract, verb inventory, reflexes-to-drop, pitfalls |
references/accessibility-and-input.md | AX tree mechanics, input routing, window control, sensitive-app gate |
references/capture-and-vision.md | ScreenCaptureKit + CGS capture, Vision OCR, audio intelligence |
references/advanced-domains.md | Apple Events, container runtime, OS log, fs, URL fetch, file watch |
references/jsc-host.md | Plain JavaScriptCore host capabilities, flags, scope rules, and pitfalls |
references/monitor-and-replay.md | Native monitor sessions, replay plans, event sources |
references/command-catalog.md | Full macOS command surface with flags and examples |
references/permissions.md | TCC permissions, microphone re-poll, Dock-icon notes |
references/cdp-app.md | Electron/Chromium desktop apps via interceptor macos cdp / interceptor macos cdp app |
references/native-agent.md | In-process native app runtime control via interceptor macos runtime |
When To Switch Surfaces
If the target is inside a browser page (DOM, network, SPA state, browser monitor, scene graph of a rich editor) - load interceptor-browser instead.
If the target is inside an Electron/Chromium desktop app's web contents (Slack, VS Code, Notion, Descript, etc.) - use references/cdp-app.md, not AX screenshots.
If the target is inside a native app's runtime (AppKit/SwiftUI object graph, selector calls, rendered text changes, hooks, MapKit state) - use references/native-agent.md. AX is still the fallback projection when the in-process agent is unavailable.
Do Not Default To Troubleshooting
- User wants a macOS task completed → run Interceptor commands.
- User wants Interceptor fixed, installed, or explained → that's a separate task; ask before diving into repo state.
- Inside the Interceptor repo, use this skill for live macOS validation, not as the primary source of repo-development instructions.