https://github.com/ctoldigital/axuse
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Badge for your README
Markdown
[](/listings/ctoldigital--axuse)HTML
<a href="/listings/ctoldigital--axuse"><img src="/api/listings/ctoldigital--axuse/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
You need **Node.js 22+** and a Chromium-family browser (Chrome, Edge, Chromium, or Chrome for Testing; found automatically, or set `AXUSE_BROWSER=/path/to/chrome`). On a bare server with no browser and no sudo: `node src/cli.js install-browser` provisions a pinned Chrome for Testing under `~/.cache/axuse` — nothing else: axuse has no npm dependencies.
**1. Get it and check the environment**
git clone https://github.com/ctoldigital/axuse.git cd axuse node src/cli.js doctor # finds a browser, launches it, takes a snapshot
For a daily Chrome/Edge session, use the guided bridge setup. It registers the native host, opens the extensions page, prints the exact folder to load, and can print your harness configuration in the same command:
node src/cli.js setup --browser chrome --harness codex
After clicking **Load unpacked** once, verify the connection with:
node src/cli.js bridge verify
**2. Add it to your harness** (use your absolute path to `src/cli.js`)
# Codex codex mcp add axuse -- node /abs/path/axuse/src/cli.js mcp # Claude Code claude mcp add --scope user axuse -- node /abs/path/axuse/src/cli.js mcp # OpenCode, Antigravity, any other MCP host: print the config block to paste node src/cli.js print-config --harness opencode # or agy | generic
**3. Ask for something in the browser**
> Open https://example.com, find the "More information" link and tell me > where it goes.
The agent calls `ax_open`, reads the accessibility snapshot, and acts on element refs like `[ref=e7]`. Each action returns only what changed.
**Optional settings** (environment variables for the MCP server)
| variable | effect | |---|---| | `AXUSE_SERVER_MODE` | `auto` (default): on a display-less Linux server, boot a private Xvfb and keep Chrome fully **headed** on it (anti-bot-safe; see [Servers, no desktop](docs/server-mode.md)) | | `AXUSE_DISPLAY_SIZE` | virtual display geometry for server mode (default `1920x1080x24`; `random` = a stable geometry per machine, so a fleet is not all 1920x1080) | | `AXUSE_TIMEZONE` | IANA `TZ` for the Chrome process — `Date`/`Intl` in pages and workers match the egress persona (validated by `doctor`) | | `AXUSE_LANG` | `--accept-lang` for Chrome — `navigator.language(s)` and the `Accept-Language` header match the egress persona | | `AXUSE_PROXY` | route every launched browser through a proxy (`http://`·`socks5://`, credentials supported — answered over CDP); `ax_open {proxy}` sets it per launch, and `ax_open {timezone, lang}` completes the per-instance persona | | `AXUSE_AMBIENT_MOTION` | `0` disables idle pointer park-fuzz (default: automatic in server mode — the agent's "thinking" pauses still show a live hand) | | `AXUSE_MAX_BROWSERS` / `AXUSE_MAX_TABS` | governance caps for massive operations (defaults 8 / 48) — typed failures instead of OOM spirals | | `AXUSE_NO_SANDBOX=1` | force `--no-sandbox` (auto for root/container server runs) | | `AXUSE_NEUTRALIZE_WEBDRIVER=0` | disable the `navigator.webdriver` posture-fix fallback (the `AutomationControlled` launch flag already fixes it at the source) | | `AXUSE_HEADLESS=1` | launch the browser without a window — **trusted internal pages only**: challenge/anti-bot pages detect headless first; servers get server mode instead | | `AXUSE_BROWSER` | path to the browser binary | | `AXUSE_PROFILE_DIR` | where temporary browser profiles go (default: OS temp; they are deleted on exit) | | `AXUSE_BRIDGE_DIR` | override the local bridge state directory (default: `~/Library/Application Support/axuse` on macOS) | | `AXUSE_ENABLE_MACOS_CUA=1` | enable macOS desktop tools (Accessibility + Screen Recording grants are still required) | | `AXUSE_BRIDGE_DEBUG=1` | trace the extension bridge |
To drive your own logged-in Chrome instead of a fresh browser, see [Driving your daily browser](#driving-your-daily-browser-the-codex-pattern).
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
SKILL.md · Manifest · 179 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.
- # axuse — browser & computer use, done right
- Accessibility-first browser/computer use over MCP. Works in any MCP-capable
- harness (Codex, Claude Code, OpenCode, Antigravity, …). Zero dependencies.
- ## The contract (read once, then act)
- **Instrument, don't photograph.** The browser is controlled through CDP with
- structured accessibility snapshots. Screenshots are rationed. Coordinates are
- the last resort.
- 1. **Open → act → read the diff → act.** Every action returns the diff of
- what changed — you do not need to re-observe after acting. Elements carry
- their state: `checked`/`unchecked`, `expanded=…`, `selected`, `disabled`,
- `value="…"`, `haspopup`. Tables print one `row "a | b | c"` line per row.
- 2. **Batch, don't drip.** Forms: ONE `ax_fill` with every field (text,
- `<select>`, checkboxes/radios/switches as true/false, ARIA/native sliders as numbers (trusted Arrow-key convergence, no synthetic writes), custom dropdowns and
- autocomplete comboboxes by option text) plus `submit` — not one call per
- field.
- 3. **Search, don't scroll-and-read.** `ax_observe {find:"text"}` returns only
- the matching lines (+context, refs) from the whole page.
- `ax_scroll {until:"text"}` scrolls an infinite feed / lazy list in ONE call
- until the text appears and returns just that neighbourhood.
- 4. **Refs, not pixels.** Act on `{ref: "e7"}` from the latest observation.
- Refs are bound to the element and resolved live (after the element's box is
- stable), so clicks land even if the layout moved.
- 5. **Frames and tabs are handled for you.** Cross-origin iframes appear as
- `--- frame f1 (url) ---` sections with `f1:e3` refs — act on them like any
- ref. A click that opens a new tab/popup reports it and returns the new
- tab's snapshot; it becomes the active tab (`tab_id` to go back).
- 6. **Dialogs.** An action that opens alert/confirm/prompt says so in its
- result; answer with `ax_dialog` (accept|dismiss, `prompt_text`). A
- confirm→prompt chain reports the next dialog after each answer.
- 7. **Waiting.** `ax_wait_for {text|selector|expression}` is one bounded
- in-page wait and returns the diff when the condition holds.
- 8. **Pixels only when pixels matter** (canvas, visual checks): the snapshot
- shows `canvas (box=x,y,WxH)`; take one `ax_screenshot`, then click
- `{x,y}` in page coordinates (the box tells you where the canvas is).
- 9. **App shortcuts follow the OS.** `ax_press {combo:"ctrl+alt+1",
- platform:true}` translates Windows-convention application shortcuts to
- the host OS (macOS: cmd+alt+1, cmd+end, …). Omit `platform` for combos
- that must be literal Control (terminals, devtools). Plain `enter`,
- `escape`, arrows are identical everywhere; select-all is automatic.
- For a bounded source list, use `ax_open_many` with `urls: [...]`. It returns
- compact title/status/excerpt rows and closes its temporary tabs by default;
- reserve repeated `ax_open` calls for pages that need interactive follow-up.
- ## CAPTCHA solving (only with a loaded solver plugin)
- `ax_solve_captcha { provider, url? }` solves a CAPTCHA on the active tab (or
- opens `url` first) using a **loaded solver plugin** — the open core ships none;
- solvers are separate (paid) packages. `ax_plugins` lists what is loaded and any
- that failed to load. Results are facts: `solved`, `token`, `attempts`,
- `rounds`, `elapsedMs`, `notes` — a null token is reported as unsolved, never
- fabricated. Without any solver loaded the call fails typed `NO_SOLVER` with the
- install hint.
- Loaded plugins may also contribute **capability tools** (`ax_vault`,
- `ax_net`, `ax_capture`, `ax_guard`, `ax_extract`, …) through a validated
- `tools()` export — capability surfaces, not solves. `ax_plugins` lists each
- loaded package together with its contributed tool names.
- **Servers (no desktop):** on a display-less Linux host axuse auto-boots a
- private Xvfb and keeps Chrome fully **headed** on it — never pass
- `headless: true` for challenge/anti-bot pages (they check headless first).
- The `ax_open` result reports the fact: `display: :N (virtual …)`. Persona
- coherence with the egress persona is configured server-side
- (`AXUSE_TIMEZONE`, `AXUSE_LANG`, `AXUSE_PROXY`; `navigator.webdriver`
- stays `false` via the `AutomationControlled` launch flag). For
- dynamics-sensitive targets pass `human: true` on `ax_click` (jittered
- curved mouse approach) and `ax_type` (per-key cadence) — solver plugins
- already use it on challenge widgets. Solvers work unchanged; vision needs
- `<PREFIX>_VISION_KEY` (any OpenAI-compatible endpoint) or the owner-only
- `~/.config/axuse/secrets.json`. Full lane: `docs/server-mode.md`.
- ## Error vocabulary (typed — read `code`, `hint`, `retry`)
- - `REF_NOT_FOUND` / `STALE_STATE` → the page changed under you: `retry:
- "reobserve"` — call `ax_observe`, then re-plan from fresh refs.
- - `DIALOG_OPEN` → answer with `ax_dialog`, then retry the action.
- - `ELEMENT_HIDDEN` → scroll or re-observe.
- - `SCREENSHOT_BUDGET_EXCEEDED` → crop a region instead.
- - `DESKTOP_PERMISSION_REQUIRED` → grant macOS Accessibility/Screen Recording
- to the host, then retry after `axuse doctor` confirms the grant.
- - Actions report `action_sent`: `sent` | `possibly_sent` (a timeout after
- dispatch — verify state before retrying, the input may have landed).
- ## Desktop apps on macOS — structure-first too
- The macOS desktop layer (needs `AXUSE_ENABLE_MACOS_CUA=1` + the
- Accessibility grant) mirrors the browser discipline:
- 1. **`ax_desktop_windows`** → pick the target app (rows carry pid + bounds;
- frontmost first).
- 2. **`ax_desktop_ax_snapshot {pid|name|front}`** → the app's accessibility
- tree with roles, titles, values, bounds, and live refs — the desktop twin
- of `ax_observe`. Budgeted (truncation is reported as facts).
- 3. **Act on refs, not pixels**: `ax_desktop_ax_click {ref}` (trusted AXPress;
- automatic coordinate fallback when an app refuses), `ax_desktop_ax_set
- {ref, value}` (writable text fields, read-back verified), and
- `ax_desktop_ax_read {ref}` for fresh facts. Stale refs fail typed
- `REF_NOT_FOUND` with a reobserve hint — same vocabulary as the browser.
- 4. Coordinates + screenshots (`ax_desktop_click`, `ax_desktop_screenshot`)
- remain the fallback for canvas/games — the same "structure before
- pixels" rule as the browser side.
- ## Attach to the real browser (two ways)
- **1. Raw CDP attach.** Relaunch Chrome with `--remote-debugging-port=9222
- --remote-allow-origins=*`, then `ax_open { url, cdp_url: "http://127.0.0.1:9222" }`.
- Full feature set (including OOPIF frame entry).
- **2. The axuse bridge extension (Codex-style).** Drive your daily Chrome/Edge
- through an extension — your real profile, cookies and logged-in sessions, with
- the debugger infobar keeping you honestly informed:
- ```
- axuse setup --browser chrome --harness codex # guided one-time setup
- axuse bridge verify # check the live connection
- axuse bridge install # registers the native messaging host
- axuse bridge # start the hub (or it starts on demand)
- ```
- Then load `bridge/extension` as an UNPACKED extension in Chrome
- (chrome://extensions → Developer mode → Load unpacked), and
- `ax_open { url, backend: "extension" }`. The service worker dials the hub via
- native messaging; tabs it opens are visible in your browser; `ax_close` closes
- the tabs axuse created — never your browser.
- **Extension backend notes (all discovered live):**
- - Branded Chrome 137+ ignores `--load-extension` (silent no-op), so automated
- installs need Edge / Chromium / Chrome-for-Testing. Loading unpacked by hand
- works in every browser.
- - Edge's native-messaging host lookup requires `allowed_origins`
- (`chrome-extension://ID/`) in the host manifest — `allowed_extensions` alone
- reports "host not found". The installer writes both fields.
- - On macOS, `--browser` may also be `chromium` or `chrome-for-testing`; the
- installer uses the browser-specific `NativeMessagingHosts` directory.
- - On Windows the native host is a `.bat` launcher (cmd.exe relays the stdio
- pipes faithfully; a compiled C# shim lost Chrome's stdin writes).
- ## Desktop (computer use)
- `ax_desktop_*` tools exist on **Windows** (SendInput + GDI capture, physical
- pixels — get bounds from `ax_desktop_screen_info`/`ax_desktop_windows`).
- Verified live.
- **Linux** mounts the same tools automatically on X11/XWayland sessions
- (`DISPLAY` set): XTEST input, GetImage JPEG capture, EWMH window list and
- activation, RandR per-monitor layout in `ax_desktop_screen_info` — and the
- **structure-first layer through AT-SPI** (zero-dependency D-Bus client):
- `ax_desktop_ax_snapshot/ax_click/ax_set/ax_read` with refs, roles, names,
- bounds and states, like macOS System Events. No extra packages; headless
- hosts are covered by server mode's auto-booted Xvfb (`xvfb-run` also works).
- Coordinates are root-window pixels. Screenshots honor
- the byte budget with a quality → quality → downscale ladder (vision keeps a
- usable image instead of a dead end), and `ax_desktop_type` pastes long or
- non-keymap text through the clipboard when xclip is present (reported
- honestly as `via: "clipboard-paste"`).
- **macOS** ships an opt-in driver (System Events keystroke, corrected
- CoreGraphics mouse/scroll events via JXA, and `screencapture` + `sips` pixels)
- that loads with `AXUSE_ENABLE_MACOS_CUA=1`. It reports TCC permission failures
- as typed desktop errors. Grant the host Accessibility + Screen Recording in
- System Settings → Privacy & Security, then use `node src/cli.js doctor` before
- desktop actions. Coordinates are macOS global display points; desktop JPEGs
- are resized to those point dimensions for direct coordinate mapping.
- v1 desktop is coordinate+vision based (no OS accessibility tree): use it only
- for apps the browser tools cannot reach. Prefer `ax_*` for anything web.
- ## Anti-patterns
- - Screenshot loops as the primary observation (the CUA trap — expensive,
- lossy, coordinate-drifting).
- - Clicking coordinates remembered from BEFORE another action or navigation.
- - Polling with repeated full observations when a `diff` would do.
- - Ignoring `covered: true` notes (an overlay ate the click) — verify in the
- diff and re-plan.
README.md · README · 454 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.
- # axuse — browser & computer use, done right
- **Accessibility-first browser and computer use for agent harnesses.** One MCP
- server plugs into Codex, Claude Code, OpenCode, Antigravity, or any
- MCP-capable host. Zero dependencies (Node ≥ 22). Windows desktop driver is
- verified; macOS desktop control is available as an explicit opt-in with
- native TCC permission checks; Linux desktop control runs over X11/XWayland
- (XTEST input + capture + EWMH windows, zero extra packages).
- The design is distilled from the two best implementations of this problem —
- OpenAI's Codex Chrome extension and the ZCode harness — and exists to prove a
- point: **a screenshot loop is not the right interface for a machine**. The
- DOM tree, the accessibility tree, and CDP are. axuse instruments the target
- instead of photographing it.
- **Not a developer?** You don't need anything below. In the Claude desktop
- app, download `axuse.mcpb` from [ax-use.com](https://ax-use.com) and
- double-click it. In ChatGPT's Codex app, Claude Code, Cursor or any other
- agent, paste the [install prompt](https://ax-use.com/install.md) and the
- agent sets axuse up for you. See the
- [non-developer guide](docs/non-developer-onboarding.md).
- ## Three ways to let an agent work for you
- One install, three surfaces. In all three the agent reads the screen as **text from the accessibility tree**, not as a screenshot it has to interpret, so it is faster, cheaper and less likely to misclick.
- ### Best way to get started
- Let your agent do it. Paste one line into Codex, Claude Code, ChatGPT Work, Cursor, OpenCode, Devin, Antigravity or any MCP-capable agent:
- - Browser use and computer use: *Install axuse by following https://ax-use.com/install.md*
- - Phone use (Android): *Install axdroid by following https://ax-use.com/install-phone.md*
- Claude desktop users can instead download `axuse.mcpb` from [ax-use.com](https://ax-use.com) and double-click it. Developers: see the [Quick start](#quick-start) below.
- ### Browser use
- Your agent drives Chrome, Edge or Chromium: your signed-in daily browser through the extension bridge, or a clean one.
- - **Why it is better:** it reads the DOM and accessibility tree over CDP as a compact text snapshot with stable element refs, and every action returns only what changed. Input is trusted CDP input, and failures are typed errors with retry hints. See [why this beats screenshot CUA](#why-this-is-faster-and-more-reliable-than-screenshot-cua).
- - **Benchmark:** on 16 server-scored tasks in the same harness and model, axuse's median task takes **17 s** against 26 s for Codex's own Chrome extension and 56 s for browser-use, using about half the tokens, with the same accuracy. [Details](#benchmark).
- - **Get started:** [Quick start](#quick-start).
- ### Computer use
- Your agent drives desktop apps: Windows is verified, macOS is an explicit opt-in with native permission checks, Linux runs over X11 (and on display-less Ubuntu servers, see [server mode](#servers-no-desktop-ubuntu-server-lane)).
- - **Why it is better:** the same design as browser use. The agent reads each app's operating-system accessibility tree as text and acts on refs; a screenshot is only a fallback for canvases and other screens with no tree.
- - **Benchmark:** we have not published a head-to-head desktop benchmark yet. The browser numbers above are the measured evidence for the shared design.
- - **Get started:** the install line above, then the [tool surface](#tool-surface) for the desktop tools.
- ### Phone use (Android)
- Your agent uses an Android phone through [axdroid](phone-use/android/README.md), an MCP server plus a phone app. axphone for iPhone is coming soon.
- - **Why it is better:** it reads the phone's own accessibility tree as text, so no vision model is needed. A guarded screenshot is a fallback for screens with no readable text, and the phone's owner can switch it off.
- - **Benchmark:** a Codex agent (gpt-6.1-terra) using axdroid completed **116 of 116** tasks of the official AndroidWorld suite, repeated three times. Median 66 s and 223k input tokens per task, and no screenshots needed. [Results](phone-use/android/androidworld/README.md).
- - **Get started:** the `install-phone.md` line above. You need an Android 8+ phone, a USB cable and an MCP-capable agent.
- ## Proven in production
- axuse is maintained by **CTOL Digital Solutions**
- ([ctol.digital](https://ctol.digital)), a leading AI, Strategy and IT
- consultancy. This work has been tested and used at large scale across many
- client engagements. CTOL Digital Solutions holds the copyright of all the
- code.
- ## Quick start
- You need **Node.js 22+** and a Chromium-family browser (Chrome, Edge,
- Chromium, or Chrome for Testing; found automatically, or set
- `AXUSE_BROWSER=/path/to/chrome`). On a bare server with no browser and no
- sudo: `node src/cli.js install-browser` provisions a pinned Chrome for
- Testing under `~/.cache/axuse` — nothing else: axuse has no npm dependencies.
- **1. Get it and check the environment**
- ```bash
- git clone https://github.com/ctoldigital/axuse.git
- cd axuse
- node src/cli.js doctor # finds a browser, launches it, takes a snapshot
- ```
- For a daily Chrome/Edge session, use the guided bridge setup. It registers the
- native host, opens the extensions page, prints the exact folder to load, and
- can print your harness configuration in the same command:
- ```bash
- node src/cli.js setup --browser chrome --harness codex
- ```
- After clicking **Load unpacked** once, verify the connection with:
- ```bash
- node src/cli.js bridge verify
- ```
- **2. Add it to your harness** (use your absolute path to `src/cli.js`)
- ```bash
- # Codex
- codex mcp add axuse -- node /abs/path/axuse/src/cli.js mcp
- # Claude Code
- claude mcp add --scope user axuse -- node /abs/path/axuse/src/cli.js mcp
- # OpenCode, Antigravity, any other MCP host: print the config block to paste
- node src/cli.js print-config --harness opencode # or agy | generic
- ```
- **3. Ask for something in the browser**
- > Open https://example.com, find the "More information" link and tell me
- > where it goes.
- The agent calls `ax_open`, reads the accessibility snapshot, and acts on
- element refs like `[ref=e7]`. Each action returns only what changed.
- **Optional settings** (environment variables for the MCP server)
- | variable | effect |
- |---|---|
- | `AXUSE_SERVER_MODE` | `auto` (default): on a display-less Linux server, boot a private Xvfb and keep Chrome fully **headed** on it (anti-bot-safe; see [Servers, no desktop](docs/server-mode.md)) |
- | `AXUSE_DISPLAY_SIZE` | virtual display geometry for server mode (default `1920x1080x24`; `random` = a stable geometry per machine, so a fleet is not all 1920x1080) |
- | `AXUSE_TIMEZONE` | IANA `TZ` for the Chrome process — `Date`/`Intl` in pages and workers match the egress persona (validated by `doctor`) |
- | `AXUSE_LANG` | `--accept-lang` for Chrome — `navigator.language(s)` and the `Accept-Language` header match the egress persona |
- | `AXUSE_PROXY` | route every launched browser through a proxy (`http://`·`socks5://`, credentials supported — answered over CDP); `ax_open {proxy}` sets it per launch, and `ax_open {timezone, lang}` completes the per-instance persona |
- | `AXUSE_AMBIENT_MOTION` | `0` disables idle pointer park-fuzz (default: automatic in server mode — the agent's "thinking" pauses still show a live hand) |
- | `AXUSE_MAX_BROWSERS` / `AXUSE_MAX_TABS` | governance caps for massive operations (defaults 8 / 48) — typed failures instead of OOM spirals |
- | `AXUSE_NO_SANDBOX=1` | force `--no-sandbox` (auto for root/container server runs) |
- | `AXUSE_NEUTRALIZE_WEBDRIVER=0` | disable the `navigator.webdriver` posture-fix fallback (the `AutomationControlled` launch flag already fixes it at the source) |
- | `AXUSE_HEADLESS=1` | launch the browser without a window — **trusted internal pages only**: challenge/anti-bot pages detect headless first; servers get server mode instead |
- | `AXUSE_BROWSER` | path to the browser binary |
- | `AXUSE_PROFILE_DIR` | where temporary browser profiles go (default: OS temp; they are deleted on exit) |
- | `AXUSE_BRIDGE_DIR` | override the local bridge state directory (default: `~/Library/Application Support/axuse` on macOS) |
- | `AXUSE_ENABLE_MACOS_CUA=1` | enable macOS desktop tools (Accessibility + Screen Recording grants are still required) |
- | `AXUSE_BRIDGE_DEBUG=1` | trace the extension bridge |
- To drive your own logged-in Chrome instead of a fresh browser, see
- [Driving your daily browser](#driving-your-daily-browser-the-codex-pattern).
- ## Servers, no desktop (Ubuntu server lane)
- axuse runs under agent CLIs (codex, claude code, opencode) on headless
- Ubuntu servers. Challenge/anti-bot pages check *is this a headless browser?*
- first, so server mode never uses `--headless`: it boots a private Xvfb and
- runs Chrome **fully headed** on it — real headed build, no headless
- fingerprint (verified live against Turnstile: `ax_solve_captcha` solves on a
- server with no desktop, and the slider engine's human-curve drags land
- 10/10). Beyond headed-vs-headless, server mode covers **persona
- coherence** (`AXUSE_TIMEZONE`/`AXUSE_LANG` matching the egress persona,
- `AXUSE_DISPLAY_SIZE=random` fleet diversity, `--disable-blink-features=
- AutomationControlled` so `navigator.webdriver` stays `false` at the source)
- and fleet hygiene (zombie-Xvfb sweep). Solver plugins that need vision call
- a multimodal model through any OpenAI-compatible API; keys come from env
- vars or an owner-only secrets file. One-time setup, systemd wiring, env
- reference and scale notes: [`docs/server-mode.md`](docs/server-mode.md) —
- and `node src/cli.js doctor` verifies the whole lane (it prints the measured
- anti-bot posture and persona).
- ## Benchmark
- On 16 server-scored browser tasks, run in the same harness (Codex CLI) with
- the same model against Codex's own Chrome extension and
- [browser-use](https://github.com/browser-use/browser-use) 0.13:
- | | axuse | Codex + Chrome extension | browser-use |
- |---|---|---|---|
- | tasks passed | 28/28 | 27/27 | 27/27 |
- | median time per task | **17 s** | 26 s | 56 s |
- | tokens, all runs | **4.7M** | 9.8M | 8.8M |
- | median tool calls | **5** | 7 | 12 |
- Accuracy tied on those tasks. A harder 7-task extension (checkout flow,
- virtualized grid, date pickers, signup errors, nested iframes, file upload,
- local dev app) has been run once so far: axuse 7/7; Codex + Chrome failed 2
- by stopping to ask for confirmation; browser-use failed 1. Method, anti-cheat
- rules and how to reproduce: [`bench/suite/README.md`](bench/suite/README.md).
- Install footprint and setup comparison: [`bench/suite/EASE.md`](bench/suite/EASE.md).
- **Phone use (Android).** A Codex agent (gpt-6.1-terra) using axdroid completed
- all 116 tasks of the official AndroidWorld suite, repeated three times: median
- 66 s and 223k input tokens per task, 1,576 tool calls, no screenshots needed.
- Per-task numbers and method: [`phone-use/android/androidworld/`](phone-use/android/androidworld/README.md).
- ## Why this is faster and more reliable than screenshot CUA
- | | Screenshot CUA loop | axuse |
- |---|---|---|
- | Observation | ~1–2MB base64 raster per step, ~1k+ image tokens, vision-encoder latency | YAML-like AX snapshot in KBs; **diff by default** (only removed/added/changed lines) |
- | Targeting | pixel coordinates guessed from an image; drifts with resolution/DPR | stable element refs bound to **element identity** (insertion-safe) + Playwright-style semantic lines |
- | Input | synthetic DOM events (rejected by sites) or fragile OS injection | trusted CDP `Input.dispatch*` events (`isTrusted`) |
- | Failure mode | silent misclick, discovered 2–3 screenshots later | typed errors: `REF_NOT_FOUND` / `STALE_STATE` / `DIALOG_OPEN` with `retry` hints and `action_sent` facts |
- | Change detection | re-photograph everything | sequenced event ring buffer + snapshot diffing |
- | Cost control | none | budgets enforced in code: snapshot char/node caps, screenshot byte budget with quality fallback, one raster per call |
- ## Install into a harness
- ```bash
- node src/cli.js print-config --harness codex # or claude-code | opencode | agy | generic
- ```
- - **Codex** — append the printed `[mcp_servers.axuse]` block to `~/.codex/config.toml`
- - **Claude Code** — `claude mcp add --scope user axuse -- node <path>/src/cli.js mcp`
- - **OpenCode** — merge the printed `mcp` block into `opencode.json`
- - **Antigravity / any MCP host** — the printed `mcpServers` block
- Verify the environment: `node src/cli.js doctor`.
- The model-facing usage contract lives in [`SKILL.md`](SKILL.md) — point your
- harness's skill system (or system prompt) at it.
- ## Solver plugins (open core ↔ paid solvers)
- axuse's core is CAPTCHA-agnostic and ships **no solvers**. Turnstile / hCaptcha /
- reCAPTCHA solvers are **separate, commercially licensed packages** that plug in
- through a thin, frozen seam (`src/plugins/`):
- ```bash
- # install: drop a solver package into plugins/ (or list dirs in AXUSE_PLUGINS)
- node src/cli.js plugins # → ✓ captcha-pro@1.0.0 — providers: turnstile, recaptcha-v2, hcaptcha
- node src/cli.js solve turnstile --url https://demo.turnstile.workers.dev/
- ```
- From any MCP harness: `ax_solve_captcha { provider, url? }` and `ax_plugins`.
- Plugins that own capabilities (session vaults, network governors, guarded
- actions…) can also contribute their **own MCP tools** through a validated
- `tools()` export (`ax_vault`, `ax_net`, `ax_guard`, …) — same seam, same
- trust boundary. The ABI, the solver context, the `tools()` contract, and
- packaging/licensing guidance:
- [`docs/plugins.md`](docs/plugins.md). A complete free (PolyForm Noncommercial
- 1.0.0) reference solver
- lives in [`examples/plugin-turnstile-demo/`](examples/plugin-turnstile-demo/).
- ## Architecture
- ```
- harness (Codex / Claude Code / OpenCode / Antigravity / …)
- │ MCP over stdio (JSON-RPC 2.0) — the universal integration layer
- ▼
- src/mcp/ — thin, stateless-per-call adapter (hand-rolled, zero deps)
- │ one frozen command contract (src/core/commands.js)
- ▼
- src/core/ — the state owner (Codex native-host / ZCode host pattern)
- ├─ controller.js sessions, tabs, state_id, dialogs, auto-observe diffs,
- │ OOPIF frame registry (f-slot namespaced refs)
- ├─ cdp.js launch/attach Chromium, browser-level WebSocket, flat sessions,
- │ Target.setAutoAttach for OOPIF auto-entry
- ├─ serialize.js injected AX serializer: element-identity refs, shadow DOM,
- │ same-origin iframes (coordinate-translated), budgets
- ├─ diff.js per-ref diff + text-line multiset diff + cost-based full fallback
- ├─ actuate.js trusted Input.dispatch*, live ref resolution (frame-chain
- │ coordinate translation), combos, waits
- ├─ screenshot.js one raster, byte budget, quality fallback, crop hints
- └─ errors.js typed codes, retry hints, action_sent, side_effect
- │
- ├─ src/bridge/ — Codex-style extension backend for the user's daily
- │ Chrome/Edge: hub (TCP rendezvous, token auth, NDJSON) ←
- │ native-messaging host (framed stdio relay) ← MV3 extension
- │ (chrome.debugger = real CDP over the user's real browser)
- │ + installer (registry/HKCU, host manifest, launcher) + backend
- │ duck-typed onto the same command contract
- ▼
- src/desktop/ — computer use (driver matrix)
- ├─ Windows: resident PowerShell + SendInput/GDI, DPI-aware — VERIFIED
- ├─ macOS: JXA/CoreGraphics + System Events + screencapture/sips,
- │ display-point coordinates, env-gated with TCC diagnostics
- └─ (the driver interface is the seam for a real AX/UIA tree driver)
- ```
- ### The patterns, and where each one comes from
- | Pattern | Codex lineage | ZCode lineage | axuse implementation |
- |---|---|---|---|
- | Diff-first observation | page-state diffing, default-on | "the tree comes back as a diff only… unchanged rows are omitted and their indices stay valid" | per-ref diff; refs bound to element identity so unchanged rows stay valid |
- | Element addressing | axState `element_index`/locators | refs `e1,e2…` in page + live resolution | `window.__axuseRefRegistry` (identity-stable across insertions), resolved live at action time |
- | Trusted input | `chrome.debugger` → `Input.dispatch*` | `webContents.debugger` | raw CDP `Input.dispatch*` / `Input.insertText` |
- | Event buffer | `tab_cdp_events` sequenced ring (limit ≤1000) | event routing with teardown discipline | ring buffer, sequence cursor, filtered methods |
- | Context budgets | 64k DOM text cap | 2×200KB images at protocol boundary, one-raster rule | snapshot node/char caps; screenshot 200KB budget + quality fallback + crop hint |
- | Error vocabulary | structured locator errors | `STALE_STATE`, `sideEffect:none\|uncertain`, `actionSent` | typed codes + `retry: reobserve\|retry\|never` + `action_sent` |
- | Frozen contract | command envelopes w/ zod | one discriminated union for all backends | `Contract` → validation AND MCP schemas generated from it |
- | Real user session | attaches to the user's real Chrome profile | `extension` backend via user Chrome | **extension bridge**: MV3 extension + native messaging + hub; `ax_open {backend:"extension"}` |
- | Frame entry (OOPIF) | webmcp/extension content merging | IAB merges frames; OOPIF via CDP | `Target.setAutoAttach` per tab; frames serialized in their own sessions, merged under `f<slot>:` identity-stable refs, input dispatched frame-locally |
- ## Tool surface
- **Browser** (always): `ax_open`, `ax_open_many`, `ax_navigate`, `ax_go`, `ax_tabs`, `ax_observe`,
- `ax_click`, `ax_fill`, `ax_upload`, `ax_hover`, `ax_type`, `ax_press`,
- `ax_scroll`, `ax_select`, `ax_drag`, `ax_screenshot`, `ax_element_info`,
- `ax_evaluate`, `ax_wait_for`, `ax_events`, `ax_dialog`, `ax_close`.
- The ones that save the most steps:
- - `ax_fill` sets a whole form in one call (text, selects, checkboxes, radios,
- switches, custom dropdowns, autocomplete) and can click submit.
- - `ax_observe {find:"text"}` returns only the matching lines of a big page.
- - `ax_scroll {until:"text"}` scrolls an infinite feed or virtualized list,
- in the page or inside a scrolling panel, until the text appears.
- - `ax_upload` sets files on a file input; a click that opens a file chooser
- is reported instead of hanging.
- - `ax_open_many` opens a bounded URL list sequentially, returns compact titles
- and accessibility excerpts, and closes temporary tabs by default. It is the
- batch equivalent of `ax_open` and avoids writing a custom MCP client.
- - JS dialogs and new tabs opened by an action are reported in its result.
- **Desktop** (Windows: verified. macOS: opt-in with
- `AXUSE_ENABLE_MACOS_CUA=1` and host Accessibility/Screen Recording grants.
- Linux: automatic on X11/XWayland sessions with `DISPLAY` set):
- `ax_desktop_screenshot`, `ax_desktop_screen_info`,
- `ax_desktop_click`, `ax_desktop_type`, `ax_desktop_press`, `ax_desktop_scroll`,
- `ax_desktop_windows`, `ax_desktop_activate`, `ax_desktop_drag`.
- ## The loop the model is guided into
- ```
- ax_open → FULL snapshot with refs (e.g. button "Sign in" [ref=e7])
- ax_click {e7} → returns the DIFF (removed/added/changed + text changes)
- ax_type {e9, text} → returns the diff (value="…" appears)
- … → screenshots ONLY for visual/canvas checks (budget-capped)
- ```
- Cross-origin iframes appear in the snapshot as `--- frame f1 (url) ---`
- sections with `f1:eN` refs — same loop, same diffs, frame-stable refs.
- Errors are facts, not strings:
- ```json
- { "code": "REF_NOT_FOUND",
- "hint": "Refs are per-observation. Call ax_observe, then act on fresh refs.",
- "retry": "reobserve" }
- ```
- ## Driving your daily browser (the Codex pattern)
- ```bash
- axuse bridge install # registers the native messaging host (Chrome + Edge hives)
- axuse bridge # hub (or it starts on demand with the MCP server)
- ```
- Load `bridge/extension` unpacked in Chrome/Edge (Developer mode → Load
- unpacked), then `ax_open { url }`: while the extension is connected, an
- omitted `backend` picks it (the result reports `backend`; pin it with
- `AXUSE_BACKEND=cdp|extension`). Your browser, your
- logged-in sessions, tabs visible to you; `ax_close` closes only axuse's tabs.
- Input and navigation bring a hidden axuse tab forward first (background tabs
- get no requestAnimationFrame, so SPAs never finish wiring their handlers;
- `AXUSE_VISIBLE_GUARD=0` opts out). Tabs are shared by every caller of one
- server, so `tab_id` is required once more than one tab is controlled
- (`AXUSE_REQUIRE_TAB_ID=0` restores the implicit active tab). Tabs no call has
- touched for 30 minutes are closed (`AXUSE_TAB_IDLE_MS`, `0` = off), and the
- hub closes the tabs of a client process that disconnects. Top-level HTML/text
- `data:` URLs load through `Page.setDocumentContent` on this backend (Chrome
- refuses the navigation); other `data:` types need localhost. For long
- articles whose snapshot is cut or shortened, `ax_observe {mode:"text"}`
- returns the full readable text.
- The whole chain — native messaging framing, hub auth, CDP-over-chrome.debugger,
- diffed snapshots, trusted clicks — is covered by `test/bridge.test.js`.
- Field notes (all established live against Edge 155 / Chrome 155):
- - Branded Chrome silently ignores `--load-extension` (137+). Automated
- extension loads need Edge / Chromium / Chrome-for-Testing; manual unpacked
- loads work everywhere.
- - Edge requires `allowed_origins` in the host manifest — with only
- `allowed_extensions` it reports "native messaging host not found". The
- installer writes both.
- - On macOS, `setup` and `bridge install` also accept `chromium` and
- `chrome-for-testing`, and register the host in each browser's own
- `NativeMessagingHosts` directory.
- - The Windows native host is a `.bat` launcher: cmd.exe relays the framed
- stdio pipes faithfully, where a compiled C# shim (Console.OpenStandardInput)
- dropped Chrome's stdin writes. Debug any install with
- `AXUSE_BRIDGE_DEBUG=1` (hub + nm-host message tracing) and
- `self.__axuseDiag` inside the extension's service worker (readable via an
- attached DevTools/CDP session).
- ## Honest scope notes
- - **macOS desktop control is opt-in** because it can synthesize OS input. Set
- `AXUSE_ENABLE_MACOS_CUA=1`, grant the host Accessibility and Screen Recording
- in System Settings → Privacy & Security, then run `node src/cli.js doctor`.
- Coordinates are macOS global display points and returned desktop JPEGs are
- resized to the same point dimensions for direct click mapping. Linux desktop
- control mounts automatically on X11/XWayland sessions (needs `DISPLAY`;
- Xvfb works for headless hosts) — and it is structure-first too: the AT-SPI
- tree (via axuse's zero-dependency D-Bus client) mounts
- ax_desktop_ax_snapshot/ax_click/ax_set/ax_read like macOS, plus EWMH
- windows, RandR monitor layout, a screenshot budget ladder that downscales
- instead of erroring, and clipboard-paste typing when xclip is installed.
- - **The extension backend has no Target domain** (chrome.debugger limits), so
- OOPIF frames are listed but not entered there; the CDP backend enters them.
- - **Anti-bot reality**: axuse runs a real Chromium with a real profile, but
- it does not implement Codex's `x-browser-agent` traffic labeling or
- bot-detection handoff — sites that fingerprint automation may still block
- it. The bridge backend (your daily browser) is the most human-looking path.
- For a non-MCP batch workflow, the same bounded operation is available from the
- CLI and accepts plain URL lists or Markdown containing links:
- ```bash
- node src/cli.js open-urls sources.md --backend extension --output report.md
- ```
- The generated report is intentionally honest: it contains page titles, access
- status, and bounded accessibility-text excerpts, not fabricated semantic
- summaries.
- ## Development
- ```bash
- node --test test/diff.test.js test/browser.test.js test/mcp.test.js test/desktop.test.js test/desktop-linux.test.js test/oopif.test.js test/bridge.test.js test/plugin.test.js
- ```
- On macOS, enable the passive desktop capability gates explicitly:
- ```bash
- AXUSE_ENABLE_MACOS_CUA=1 AXUSE_TEST_MACOS_DESKTOP=1 npm test
- ```
- Tests are gated: browser/MCP tests skip when no Chromium-family browser is
- found; the OOPIF test spins up two loopback origins (127.0.0.1 + localhost);
- the bridge test registers + uninstalls a native messaging host and uses an
- extension-capable browser when one is installed (branded Chrome on current
- macOS builds is honestly skipped because it ignores automated
- `--load-extension`); desktop tests exercise passive screen/window discovery on
- macOS with `AXUSE_TEST_MACOS_DESKTOP=1`. A real macOS screenshot test is
- explicit with `AXUSE_TEST_MACOS_SCREENSHOT=1` because Screen Recording is
- TCC-protected. The Linux desktop tests boot their own private Xvfb displays
- (and skip typed when Xvfb is not installed); they never touch your session.
- No test moves your real mouse or sends keys.
- Debugging: `AXUSE_BRIDGE_DEBUG=1` traces hub + native-host messages;
- `self.__axuseDiag` in the extension SW reports connect/disconnect history.
- Every `# SKIP` in a suite run is explicit, typed, and audited: run TAP output
- through `node tools/skip-audit.mjs` and it fails when a skip is missing from
- `test/skip-allowlist.json`. CI enforces this on every lane.
- macOS production reference — support matrix (browsers × macOS versions ×
- arch), TCC permission model, failure taxonomy, the manual TCC validation
- lane, benchmarks, and known limitations with evidence:
- [docs/macos-support.md](docs/macos-support.md).
- ## License
- Copyright © CTOL Digital Solutions ([ctol.digital](https://ctol.digital)).
- All rights reserved.
- Licensed under the **PolyForm Noncommercial License 1.0.0** — see
- [`LICENSE`](LICENSE). Use, distribution, and modification are free for any
- **noncommercial** purpose (personal use, research, education, charities,
- public institutions). **Commercial use requires a separate commercial
- license** from CTOL Digital Solutions ([ctol.digital](https://ctol.digital)).
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.