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. Pick per task, not per preference: | 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` or `--session` | | Drive the profile Chrome *and* record video | connect mode - `record` works over CDP in 0.27.2 (see caveat below) | | CAPTCHA, anti-bot, residential proxies, Browserbase Identity/contexts | `vd:browser` (remote escalation) | ## Prerequisites ```bash which agent-browser || npm install -g agent-browser@0.27.2 agent-browser --version # 0.27.2 pinned - the validated surface (see Verified facts) agent-browser install # one-time Chromium download; standalone --profile mode only ``` A background daemon (socket under `~/.agent-browser/`) keeps the browser alive between invocations; `idle...