1
Install the Chrome extension
Not startedOpen the BrowserMan extension in this browser profile, confirm its suggested name, and connect it to your account.
Waiting
B
Loading…
Setup state
Let's get your browser online.
Three steps. BrowserMan only starts doing things once you've connected your browser and approved the agent you trust.
2
Pick your agent
Not startedChoose the install path your agent uses today. Skill comes first by default. MCP is still a first-class path.
Choose one
3
Connect your agent
Not startedRun BrowserMan setup from your agent environment, then approve the matching request here. This is the delegated-first path.
Nothing pending yet.
Start by running BrowserMan CLI setup. Manual approval codes are still available under Advanced.
Ready state
You're live.
Your browser is online and your delegated agents are connected. BrowserMan will keep showing you what changed without making fallback keys the default path.
Browsers first
My browsers
No browsers yet.
Go back to setup and pair this browser first.
Live dashboard
Recent activity
The last 20 actions from your real BrowserMan activity history. If nothing has run yet, the empty state points back to setup.
No activity yet.
Your browser is ready, but nothing has run today. Start with SKILL.md or run npx browserman setup again from your agent if you need to reconnect.
Agents
Delegated CLI setup stays first. Manual keys remain available here when you need them.
Delegated access
CLI authorized agents
Agents you approved through the CLI-first device flow.
No CLI authorized agents yet.
Connect one from the setup state first. BrowserMan only counts delegated agents as fully ready.
Manual fallback
Key authorized agents
Manual keys for advanced cases when the delegated setup path is unavailable.
No key-authorized agents yet.
Create one only if the delegated setup path is unavailable.