Browser automation CLI for AI agents
Copy the install, test the workflow, then decide if it earns a permanent slot.
Fresh repo activity plus visible builder pull. This is the kind of tool people test before it turns obvious.
Copy the install, test the workflow, then decide if it earns a permanent slot.
Reasonable to try, but it will take more than a quick skim to get real signal.
GitHub health 37/100. no security policy. 433 open issues plus stale maintenance signal push this into high-risk adoption territory.
AI Agent
Universal
Model
Multiple
Build Time
Days
Fastest way to find out if agent-browser belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
git clone https://github.com/vercel-labs/agent-browser ~/.claude/agents/agent-browserRun this first. You will know quickly if the workflow earns a permanent slot.
rm -rf ~/.claude/agents/agent-browserNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude/ ├─ commands/ ├─ agents/ │ └─ agent-browser/ ← installs here └─ settings.json
Browser automation CLI for AI agents. An open-source agent for the AI coding ecosystem.