Requirements

For npm installation, Node.js 24+ and a supported macOS, Linux or Windows system. Obtain Chrome for Testing through the official installer. Check current platform instructions before installing.

Quick start

For the npm route, use Node.js 24+ and review the official platform requirements. Install a pinned release with npm install -g agent-browser@0.39.1, then run agent-browser install to obtain Chrome for Testing. Start on an isolated test page. Installation commands are documentation, not steps executed by Boloop.

Vercel Labs’ browser automation CLI for agents: inspect accessibility snapshots, interact with controls and capture evidence. Includes a current release and a version-labelled independent comparison.

A small interface to a real browser

agent-browser exposes browser actions as shell commands. An agent can inspect a page through an accessibility snapshot, select a referenced control, and capture a screenshot. This is useful for checking a form or a changed page after coding; it does not prove an entire application works.

A practical starting sequence

Review the release and platform requirements first. For the npm route, use a compatible Node.js version, install the pinned package and its browser, then open an isolated test page. Take a snapshot, define the expected result, act on a current reference and inspect the result again. Keep screenshots when appearance matters; a text snapshot does not describe computed spacing or alignment.

Better Stack’s January 2026 introduction. The public chapter list includes snapshot and form demos; installation details may differ from the current release. We checked metadata, not the full video.Clicking connects to the video platform. Its privacy policy applies. Watch on the original site · SourceIf playback is unavailable, use the original link.

What an independent measurement adds

Koshii Takumi's DevelopersIO comparison used agent-browser 0.38.1 and Playwright 1.59.1 on a controlled page. Its useful lesson is to compare equivalent observations and waiting conditions: returning only the values needed for a check changes the result substantially. We do not turn that experiment into a general speed or token-saving guarantee for 0.39.1.

Limits and recovery

The October 13 release 0.39.1 addresses duplicate execution after a lost daemon response and can report an unknown outcome. Confirm a write or navigation result before repeating it. Use test accounts and protect any sensitive page data. The linked Better Stack video is a January 2026 introduction; its public description lists snapshot and form demos, not a validation of the current release. Boloop has not run or benchmarked this tool.

Sources and further reading

agent-browser: official repository and installationOfficial documentation · Vercel Labs
agent-browser v0.39.1: lost-response recovery fixOfficial documentation · Vercel Labs contributors
Measured output and elapsed time: agent-browser and PlaywrightUsage record · Koshii Takumi (DevelopersIO)
Claude Code Can Now Control Your Browser (Thanks to Vercel)Video · Better Stack