| name | chrome-devtools-axi |
| description | This skill should be used when the user names chrome-devtools-axi, asks to "execute npx -y chrome-devtools-axi", wants Chrome DevTools Protocol browser automation through the AXI CLI, or needs token-efficient accessibility snapshots, stale-ref-safe clicks/fills, console/network inspection, screenshots, Lighthouse, or performance traces from a Chrome session. Do NOT use for simple web search/static extraction, stealth/anti-detection browsing, or non-Chrome browser targets. |
| version | 0.1.0 |
| author | Trevin Chow |
| license | MIT |
| platforms | ["macos","linux","windows"] |
| metadata | {"hermes":{"tags":["browser","chrome","devtools","cdp","accessibility","automation","axi","cli"],"category":"browser","requires_toolsets":["terminal"]},"openclaw":{"emoji":"🧭","homepage":"https://github.com/kunchenguid/chrome-devtools-axi","requires":{"bins":["node","npx"]},"install":[{"kind":"node","package":"chrome-devtools-axi","bins":["chrome-devtools-axi"]}],"envVars":[{"name":"CHROME_DEVTOOLS_AXI_AUTO_CONNECT","required":false,"description":"Set to 1 to connect to the user's running Chrome 144+ via remote debugging instead of launching a new browser."},{"name":"CHROME_DEVTOOLS_AXI_HEADED","required":false,"description":"Set to 1 to run Chrome in headed/visible mode."},{"name":"CHROME_DEVTOOLS_AXI_CHROME_ARGS","required":false,"description":"Whitespace-separated Chrome flags forwarded to the browser; no shell-style quoting. Useful with headed GPU/WebGL/WebGPU debugging."},{"name":"CHROME_DEVTOOLS_AXI_BROWSER_URL","required":false,"description":"Existing Chrome DevTools endpoint. Supports http(s):// browserUrl or ws(s):// WebSocket endpoint."},{"name":"CHROME_DEVTOOLS_AXI_WS_HEADERS","required":false,"description":"JSON headers for authenticated ws(s) endpoints. Treat as secret-bearing and never print raw values."},{"name":"CHROME_DEVTOOLS_AXI_USER_DATA_DIR","required":false,"description":"Persistent Chrome profile directory. Skips isolated mode; use only when persistent session state is intentional."},{"name":"CHROME_DEVTOOLS_AXI_PORT","required":false,"description":"Local bridge server port. Defaults to 9224."},{"name":"CHROME_DEVTOOLS_AXI_MCP_PATH","required":false,"description":"Absolute path to a chrome-devtools-mcp script; avoids slow npx bootstrap on cold systems."},{"name":"CHROME_DEVTOOLS_AXI_BRIDGE_TIMEOUT_MS","required":false,"description":"Bridge readiness deadline in milliseconds. Defaults to 30000."}]}} |
Chrome DevTools AXI
When to use
Use this skill when the task specifically needs chrome-devtools-axi or a
Chrome DevTools Protocol browser controlled from the terminal:
- the user says
chrome-devtools-axi, chrome-devtools-mcp, AXI browser automation, or asks to run npx -y chrome-devtools-axi
- an agent needs a compact accessibility snapshot with actionable refs and command suggestions
- browser work needs console logs, network requests, screenshots, Lighthouse, heap snapshots, or performance traces in the same CLI surface
- the existing Hermes/browser stack is unavailable or the user explicitly prefers this tool
Do not use it for ordinary web search, curl-able pages, static extraction,
or stealth/anti-detection work. Use Camofox/Camoufox only when cloaking is
load-bearing. Use built-in browser tools when the task is already solved there
and the user did not name chrome-devtools-axi.
Mental model
chrome-devtools-axi is an npm CLI wrapper around chrome-devtools-mcp. The
first command starts a persistent local bridge, then later invocations reuse the
same Chrome/DevTools session. Output is AXI/TOON-style: page metadata,
accessibility snapshots, element refs, and next-step suggestions.
State lives under ~/.chrome-devtools-axi/, including the bridge PID and
snapshot-generation counter.
Setup and verification
The skill only teaches the agent how to use the tool. The actual CLI is the npm
package chrome-devtools-axi; source repo:
https://github.com/kunchenguid/chrome-devtools-axi
Prefer npx for one-off use so the CLI is installed on demand:
npx -y chrome-devtools-axi --help
npx -y chrome-devtools-axi
Use a global install only when repeated shell use matters:
npm install -g chrome-devtools-axi
chrome-devtools-axi --help
Before relying on the tool, verify the live CLI rather than assuming docs are
current:
npx -y chrome-devtools-axi --version
npx -y chrome-devtools-axi --help
If the home view says browser: no active session, open a page:
npx -y chrome-devtools-axi open https://example.com