Add the extension. Sign in.
Browser f6n is currently a prototype. A public Chrome Web Store install link is not available on this site yet. If you’ve received a prototype build, use the installation instructions that came with it.
Open the extension in the Chrome profile you want to connect, choose Sign up or sign in, and complete the hosted sign-in. The popup shows Connected when your browser is ready.
Working from the source repository?
From the repository root, build the unpacked extension:
npm ci
npm run ext:buildOpen chrome://extensions, enable Developer mode, choose Load unpacked, and select chrome-extension/dist. Use Chrome 125 or later, and follow your organization’s software policy.
Introduce your agent.
In your agent’s connector or MCP settings, add a remote server using this address:
https://browser.f6n.run/mcpThe client must support Streamable HTTP and the service’s OAuth authorization. Follow its connection prompt and sign in with the same Browser f6n account used in the extension. Review the request before granting access.
If your agent can run a local CLI and absorb a skill, point it to the concise agent guide. It explains how to use the pinned Browser f6n CLI and resume the same approval request without handling tokens.
Exact labels vary by agent. A messenger such as WhatsApp is only the conversation interface; the agent service behind it needs the compatible connector.
Start with something small.
Keep Chrome running and your computer online. Open a page you’re allowed to use and ask your agent: “Read this report and summarize the three things I should look at.”
Follow along in Chrome and compare the summary with the source. One browser profile can be connected per account; connecting another replaces the current one.
Browser access is real access.
An authorized agent can inspect and operate your connected Chrome profile. That includes reading page content, performing actions, and requesting sensitive cookies, storage, or other session data through browser tools.
Browser f6n does not add a confirmation prompt before every action. Choose an agent you trust, understand its approval settings, and review consequential work. To stop the browser connection, disable or remove the extension at chrome://extensions.
Requested page data passes through the Browser f6n relay to your agent. The relay does not persist page contents, screenshots, or browser-tool results beyond the bounded command lifecycle. Your agent provider’s handling of those results is separate.
If the connection isn’t ready.
Check the extension popup for the actual connection state. If it says Sign-in expired, sign in again. If Chrome or your computer was restarted, the session may need a fresh sign-in. For reconnecting states, confirm your network connection and use the extension’s retry action.
The website’s illustration is not a live status check. You can also open the existing setup page for the service’s connection instructions.