Claude for Chrome, ChatGPT for Chrome and Muse for Chrome each put one vendor’s agent in your browser. VibeBrowser is the browser any agent can drive: connect Muse from chat with one message carrying your full MCP connector URL — the session ID is already in the URL path, so there is no API key, no authorization header and no second secret. Muse adds Vibe Browser as a custom connector; it lives in the Muse app under Settings → Connectors → Custom connectors, and Muse can open, read, and act on pages in your real Chrome. Claude, ChatGPT, Codex and other MCP agents connect to the same browser, and local on-device models mean you are never locked to one AI vendor.
One command connects your AI tool to your real, logged-in Chrome — then hand it any browser task.
Muse lists connectors in Settings, but there is no add form. Send Muse one message with your full connector URL and Muse creates the Vibe Browser custom connector for you.
Your connector URL is a key to your browser — and it is the only one. There is no API key, no authorization header and no second secret to paste anywhere. The extension masks the URL; if it ever leaks, Regenerate session in the extension settings kills it and the old URL stops working.
After setup, Vibe Browser sits in the Muse app under Settings → Connectors → Custom connectors, where you can view and manage it.
Muse works inside the Chrome you are already logged into — not a fresh browser with no sessions.
Muse lists connectors in Settings, but there is no add form. Send Muse one message with your full connector URL and Muse creates the Vibe Browser custom connector for you.
Your connector URL is a key to your browser — and it is the only one. There is no API key, no authorization header and no second secret to paste anywhere. The extension masks the URL; if it ever leaks, Regenerate session in the extension settings kills it and the old URL stops working.
After setup, Vibe Browser sits in the Muse app under Settings → Connectors → Custom connectors, where you can view and manage it.
Muse works inside the Chrome you are already logged into — not a fresh browser with no sessions.
Once connected, Muse can list your tabs, open and read pages, click, type, fill forms, and take screenshots in your real Chrome.
Muse today, Claude, ChatGPT or Codex tomorrow: every MCP agent drives the same browser. Local on-device models plus your choice of provider — Vibe AI, Claude Max sign-in, GitHub Copilot, OpenRouter, Ollama — mean no single AI vendor owns your browser.
Ask Muse to list your open tabs and summarize the page you are reading
Have Muse open a dashboard you are logged into and pull the numbers you need
Ask Muse to fill a web form from details you give it in chat
Let Muse check a page behind a login and report what it says
Ask Muse for a screenshot of a page in your browser
Google Workspace, MCP access for other agents, reusable skills, and a secure secrets vault.
Gmail + Calendar actions built in for real workflows, not brittle APIs.
Expose your browser as an MCP server so other AI agents can drive it.
Securely connect remote agents to your logged-in browser without VPNs.
Create reusable skills and share them across your team or clients.
Internal vault with a password-fill tool that never exposes secrets to the LLM.
Works with Vibe AI, Anthropic Claude Max, GitHub Copilot, and BYOK providers.
In the Muse app: Settings → Connectors → Custom connectors. There is no add form in Settings — the setup message creates the connector, and it appears in that list, where you can view and manage it.
Yes — the URL is the whole credential: anyone who holds it can control your browser, and there is no second secret, API key or header on top of it. That is why the extension masks the URL, and why you send it only to your own Muse. If the URL ever leaks, open the Vibe extension settings → AI Agent Control, click Regenerate session — the old URL stops working — and send Muse the message again with the new URL.
List your tabs, open and read pages, click, type, fill forms, and take screenshots — in your real Chrome, including pages where you are logged in. A good first task is a read-only one: ask Muse to summarize the page you have open.
In the extension: Vibe icon → Settings → AI Agent Control. In the Relay access box, copy the full "MCP connector URL (HTTPS)" — your session ID is the segment at the end, after /mcp/. Paste the whole URL into the setup message, or replace <session-id> in the template with that segment.
Not yet. The steps follow the Muse app as it works today — one message in chat carrying your full connector URL, then the connector listed under Settings → Connectors → Custom connectors — and the screenshots come from the real app and the real extension settings. A full end-to-end run with a live Muse account is still being verified, so treat this page as a guide.
Each of those is one vendor’s agent in your browser: Claude for Chrome is Anthropic’s Claude in a Chrome side panel, ChatGPT for Chrome lets OpenAI’s ChatGPT use your browser to complete tasks, and Muse for Chrome is Meta’s personal agent in a side panel. VibeBrowser is not another agent — it is the browser itself, exposed over MCP, so any agent can drive it: Muse, Claude, ChatGPT, Codex and more, in the Chrome you are already logged into. It also runs local on-device models and lets you choose your model and provider, so you are never locked to one AI vendor.