Who it is forA team using agent-driven browser checks in CI.
The problemGlobal tools drift between machines and break CI.
The outcomeA pinned Agent Browser version invoked from package.json scripts.
What you need first
- npm, Homebrew or Cargo
- Chrome (agent-browser install downloads Chrome for Testing)
Steps
- Run
npm install agent-browserin the project, thenagent-browser install - On Linux CI install system dependencies with
agent-browser install --with-deps - Call it from package.json scripts
- Upgrade later with
agent-browser upgrade
Prompt for your agent
Add vercel-labs/agent-browser as a dev dependency, add an npm script that runs a smoke check on <url>, and wire it into our CI with install --with-deps on Linux.
Caveat.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for vercel-labs/agent-browser and "Pin Agent Browser as a project dependency for CI"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer