fennec-cualisted
Install: claude install-skill runta-dev/fennec
# fennec-cua: computer use on macOS
fennec-cua lets you see and operate this Mac's apps. Everything goes through one persistent JavaScript REPL whose `cua` object is the Codex computer-use API. You reach it either as the MCP tools `js` and `js_reset` (server `fennec-cua`), or from a shell with `fennec-cua js`. Bindings you create (`var app = ...`) persist between calls.
Prefer a CLI, a file edit or an API when one does the job; use this for real UI work.
## 1. Check the setup first
Run once per task (from a shell):
```sh
fennec-cua doctor
```
Every line should start with `ok`. If `Accessibility` or `Screen Recording` says `fail`, stop and ask the user to grant them (you cannot do it for them): the `fix:` line names the System Settings pane, and `fennec-cua permissions --request` shows the macOS prompts. After the user changes Screen Recording, run `fennec-cua quit` (the next call restarts the daemon). If `screen capture` says `fail` because macOS has not yet asked, ask the user to run `fennec-cua permissions --request` and click Allow in the alert; until then screenshots fail but the accessibility state and input work. Once everything is `ok`, make sure no macOS prompt is left on screen (ask the user to close it): a prompt in front blocks input to other apps. Not installed at all? See [references/setup.md](references/setup.md).
## 2. Two ways to call the REPL
**MCP (preferred when your client lists the `js` tool):** call `js` with `{"code": "...", "title": "Opening Te