About five minutes. At the end an agent can open a tab in your own signed-in Chrome and tell you what is on it.
Sign up with an email address, Google or GitHub. Personal accounts are free. Setting this up for a team? Create a business account instead, so you can share browsers and set rules for everyone.
Add the TabTunnel extension to the Chrome you want your agent to use. It opens a setup page that asks you three things:
While an agent is working, Chrome shows a bar saying “started debugging this browser”. That is expected, and Chrome does not let anyone hide it.
Every app uses the same address:
https://tabtunnel.dev/v1/mcp
What you do next depends on the app.
Add a custom connector, paste the address above, and approve it when a TabTunnel page opens. There is no token to create. Step by step.
Open Tokens in the dashboard and create one, named for the app that will use it. Copy it straight away — you will only see it once. Treat it like a password: anyone who has it can use your browsers.
Then add it to your app: one command for Claude Code, or a block of JSON for Cursor, Windsurf and Cline.
Ask your agent to list your browsers. If the name you gave yours comes back, you are done. If not, each app's page has a short list of what to check.
The first command can take a few seconds
When your browser has not been used for a while, the first command waits a few seconds while it reconnects. Everything after that is immediate.
Is something here wrong, or missing? Tell us.