agent-browser

Topics in the source

• agent-browser
• Prerequisites
• Connect to the shared profile Chrome (primary mode)
• Teardown - close what you launched
• Quick start
• Deterministic replay (batch)
• Auth persistence - standalone modes
• Named profiles - one per identity context

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. | 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 | 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 - do not assume the surface held. Canonical: the vd:browser-profile skill's attach wrapper, which

This is an excerpt. Refer to the complete source and its current requirements.