agent-browser

npx skills add hAcKlyc/MyAgents --skill agent-browser --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

# Browser Automation with agent-browser ## First-time Setup The CLI is **not pre-installed** with the app — install it on first use, then download Chromium. **Always run this self-check before issuing any agent-browser command in a fresh environment.** ### Step 1: Verify or install the CLI ```bash # Probe by RUNNING the CLI (not just checking PATH presence). This catches the # common case of a stale wrapper from a previous app version: it lives at # ~/.myagents/bin/agent-browser, satisfies `command -v`, but execs a deleted # bundle path → fails with "cannot find file". `--version` exercises the real # code path and triggers the install fallback when broken. agent-browser --version >/dev/null 2>&1 || npm_config_prefix="${MYAGENTS_NPM_GLOBAL_PREFIX:-$HOME/.myagents/npm-global}" npm install -g agent-browser@0.15.1 ``` The install lands in `~/.myagents/npm-global/bin/agent-browser`, which sits earlier in PATH than any legacy wrapper. MyAgents exposes `MYAGENTS_NPM_GLOBAL_PREFIX` for this command-local install instead of setting `npm_config_prefix` on the whole shell, so nvm-based user shells stay quiet. Subsequent `agent-browser …` calls find the new binary automatically. Tell the user

Probe by RUNNING the CLI (not just checking PATH presence). This catches the
common case of a stale wrapper from a previous app version: it lives at
bundle path → fails with "cannot find file". `--version` exercises the real
code path and triggers the install fallback when broken.
agent-browser --version >/dev/null 2>&1 || npm_config_prefix="${MYAGENTS_NPM_GLOBAL_PREFIX:-$HOME/.myagents/npm-global}" npm install -g agent-browser@0.15.1
Use the npx prefix on EVERY command. Do not try to alias — it won't survive.
npx -y agent-browser@0.15.1 open https://example.com
npx -y agent-browser@0.15.1 snapshot -i
npx -y agent-browser@0.15.1 click @e1
agent-browser install