GET CONNECTED

Your browser.
Your next task.

Early access. Browser-store listings are not published yet. These steps are for users who already have the hosted extension. Public installation links will appear after review.

1. Open TabCircuit in your browser

Use the browser profile you want your agent to work in. Chrome, Brave, Edge and Opera use the Chromium extension; Firefox, Developer Edition and Nightly use the Firefox build. Pin TabCircuit in the toolbar.

2. Sign in and approve this browser

Open the extension and choose Sign in. Complete Google sign-in and approve the browser connection. Return to the extension and check that it says Browser connected.

Open your TabCircuit account ↗

Signing in on the account website alone does not connect an extension. Start the browser connection from the extension’s Sign in button.

3. Connect your AI

Choose Connect your AI in that browser. Follow the instructions shown for your client. Use the setup link or command from the exact browser you intend to control; each browser has its own connection.

Claude Code and Codex have hosted setup guides. Other AI clients need support for a remote MCP service and its authorization flow. If your client asks you to authorize TabCircuit, approve the intended browser and account. Restart the client if a newly added connection does not appear.

The hosted service runs online. You do not need to install a local TabCircuit server, run a pairing listener, or leave a TabCircuit terminal open.

4. Start with a small task

Ask your agent to check its TabCircuit connection, then open a website you choose. Approve that website in the extension. Choose For this session or remembered access, and Read only or interactive access.

Keep the browser open. Use the popup or sidebar to share an existing tab, see recent actions, or pause the agent. A shared tab keeps its existing website login.

Working across browsers

Sign in to TabCircuit separately in each browser you want to use. Give browsers clear names in your account and use their own Connect your AI instructions. Renaming a browser keeps its existing connections.

When a connection needs attention

Wrong browser: inspect the connection’s selected browser and use the setup link from the intended extension.
Needs you: complete the requested step in the browser, then choose Done—resume on the task card.
Agent limit reached: pause or finish another session, or end it from your account. See how sessions are counted.
Sign-in expires: reauthorize when the client requests it. Starting a new task alone does not require a new browser setup.
Browser disconnected: keep the browser open, check the extension’s connection status and your internet connection.

Website approvals and client authorization are separate. An agent cannot grant itself access to a new website.