agent-browser

# agent-browser The primary local browser driver in this catalog. In **connect mode** it attaches over CDP to the real Chrome launched by `vd:browser-profile` - persistent human-shared login, Google OAuth in a real browser, and `vd:browser-trace` observing the same session as a second CDP client (verified coexisting). That combination is the hands of `vd:web-e2e`. Its own **`--profile` mode** remains for standalone tasks that want isolation from the shared Chrome. `vd:browser` (Browserbase) is the remote escalation for CAPTCHA/anti-bot/proxy walls, not the default driver. | Need | Use | |---|---| | e2e flows against a local app: shared login, human window, trace evidence | this skill in connect mode, via `vd:web-e2e` | | Standalone automation, scratch rendering, per-identity isolated profiles | this skill with `--profile` / `--session` | ## Prerequisites ```bash which agent-browser || npm install -g agent-browser@0.27.2 agent-browser --version # 0.27.2 pinned agent-browser install # one-time Chromium download; standalone --profile mode only ``` A background daemon (socket under `~/.agent-browser/`) keeps the browser alive between invocations; `idleTimeout` in `agent-browser.json` controls auto-shutdown. The pin is deliberate: the gotchas quoted throughout (positional screenshot path, bare `network har start`, same-origin-only mocks, `wait --url` on SPAs) were validated live against 0.27.2. Before upgrading, re-check each one against the new binary - ...