You choose how data is processed. Local models run on your device. Cloud models send data to that provider's API.

How much does Vibe Co-Pilot cost?

Vibe is free to install. If you run cloud models, usage is billed by that provider, and paid Vibe plans are optional.

How does Vibe compare to OpenClaw?

OpenClaw is a self-hosted agent stack. Vibe is a browser co-pilot focused on completing overcomplicated web tasks in your existing browser sessions.

How does Vibe compare to Claude Cowork?

Claude browser workflows are Claude-first. Vibe is browser-first and model-flexible, so teams can choose how they run automations.

How does Vibe compare to Chrome DevTools MCP?

DevTools MCP is a browser debugging/control interface. Vibe packages browser task execution into a co-pilot experience for end-to-end workflows.

Can Claude control my browser from claude.ai, not just Claude Desktop?

Yes, via a custom connector. Claude Desktop can launch a local MCP server, but claude.ai, Cowork, and mobile cannot — they need a remote MCP server reachable over the public internet. The Vibe relay is exactly that, so one connector URL covers every Claude surface.

How do I add a custom connector in Claude?

Open Settings → Connectors, click Add, then Add custom connector. Give it a name, paste https://relay.api.vibebrowser.app/mcp/ followed by your routing UUID, and click Add. Then in a chat use the + button → Connectors and toggle it on for that conversation.

Claude says "You are not connected to Vibe Browser yet" — did it fail?

No. Claude reports a custom connector as not connected until the first time a conversation actually calls one of its tools. Send a prompt that requires the browser — for example asking it to open a page — and the status resolves. If tool calls then fail, see the troubleshooting table.

Do I need to verify a domain or get allowlisted?

No. Claude needs no domain verification and no allowlist request for a custom connector, and there is no consent screen to approve — you paste the connector URL and that is the whole setup.

Does this work in a Cowork session?

Yes. A custom connector is brokered through your Claude account rather than tied to one machine, so a Cowork session reaches it the same way a Desktop chat does. A local Desktop Extension would not — that is scoped to the desktop app on that one computer.

Do I still need to install anything?

Only the Vibe Chrome extension. On the remote-connector path there is no npx command and no local MCP server — the hosted assistant talks to the Vibe relay over HTTPS, and the relay forwards to your extension.

What exactly do I paste into the connector?

One URL: https://relay.api.vibebrowser.app/mcp/ followed by your routing UUID, which you copy from the Vibe extension → Settings → Agent connection URL. There is no consent screen, no client id, no secret field and no scopes to approve — the URL is the whole configuration.

Why does this use a URL path when the /mcp docs use an X-Remote-Session header?

Because of what the client can send, not because they are different products. A full MCP client (Claude Code, Cursor, VS Code, Codex, OpenCode, Copilot CLI) lets you set request headers, so it can point at https://relay.api.vibebrowser.app/mcp and pass the routing UUID as an X-Remote-Session header — which keeps the credential out of URLs, proxy logs and browser history. A hosted connector UI (Claude on the web, ChatGPT apps) gives you one text field and no header editor, so the only place the UUID can ride is the URL path: https://relay.api.vibebrowser.app/mcp/ . Same relay, same browser, same tools. If your client can send headers, prefer the header form.

I set this up earlier with a consent screen — what do I do now?

Remove the old connector and add it again with the direct URL. In Claude: Settings → Connectors, delete the Vibe entry, then Add → Add custom connector and paste https://relay.api.vibebrowser.app/mcp/ followed by your routing UUID. In ChatGPT: go to chatgpt.com/plugins, delete the old app, then create it anew via Add → Add custom MCP server with the same URL. Editing the URL in place is unreliable because clients cache what they discovered the first time. Once re-added, no approval step appears — the connector just starts listing tools.

Is the UUID in the connector URL a secret?

Yes. That UUID is the credential that routes an agent to your browser — anyone who has it can drive your logged-in session. Treat the URL like a password: never post it in a shared chat, screenshot, README, or issue. If it leaks, regenerate it in the Vibe extension settings and the old UUID stops routing immediately.

How do I revoke access?

Two ways, either is enough. Remove the Vibe connector inside the assistant. Or open the Vibe extension → Settings and turn "Enable external AI agent control" off, which cuts every client off from this browser at once. To invalidate the URL itself, regenerate the connection URL in the extension.

What can an assistant do once it is connected?

Everything the extension exposes: list and switch tabs, read page text and HTML, take screenshots and accessibility snapshots, navigate, click, type and fill forms, scroll, use keyboard shortcuts, and open or close tabs — inside the sessions you are already logged into. Connect it only to an assistant you trust with those sessions.

What is the difference between this and the local MCP server?

The local path (npx @vibebrowser/mcp) runs on your machine and suits desktop clients that can spawn a process — Claude Desktop, Cursor, VS Code, Codex CLI. The remote path suits hosted assistants that only accept a URL. Both end up driving the same Chrome tab through the same extension.

Does my page content go through your servers on this path?

Yes — unlike the local STDIO path, tool calls and their results traverse the Vibe relay, because the assistant is running in the vendor cloud and cannot reach your machine directly. If you need page content to never leave your machine, use the local MCP server with a desktop client instead.

Vibe Browser for

Give Claude on the web control of your browser

Settings → Connectors → Add → Add custom connector. Paste your https://relay.api.vibebrowser.app/mcp/<your-routing-uuid> URL and Claude drives your real Chrome — web, Cowork and mobile.

Connector verifiedChecked October 19, 2026

Verified end to end in a real Claude account on October 19, 2026 with the direct connector URL https://relay.api.vibebrowser.app/mcp/<your-routing-uuid>: the connector is saved under Customize → Connectors, and a live prompt made Claude call List Pages and return the real open Chrome tabs.

1Install the Vibe extension in Chrome
Add Vibe AI Browser from the Chrome Web Store (Chrome, Brave, Edge, or any Chromium browser). This is the piece that lets an agent drive the browser you are already logged into — no second browser profile, no re-authentication.
2Add the connector in Claude: Settings → Connectors → Add
Copy your URL first: Vibe icon → Settings → AI Agent Control → Remote (internet) → copy the Agent connection URL. Then in Claude open Settings → Connectors, click Add → Add custom connector, name it "Vibe Browser", paste the URL, and click Add. Custom connectors need a paid Claude plan.
Vibe extension → Settings → Agent connection URLurl
```
https://relay.api.vibebrowser.app/mcp/<your-routing-uuid>
```
3Turn it on in a chat
In a chat, tap + → Connectors and turn Vibe on. Keep Chrome open with the extension running. Then ask Claude to open a page — your browser does the work.

Your relay URL / extension UUID grants live control of your browser session. Treat it like a password: never commit it or paste it into a shared chat.

Check it works

Ask Claude (web, Cowork & mobile)bash

Go to duckduckgo.com and find out when the first GPT model was released.

Expected answer: 2018

Pick this over "open google.com" because a wrong answer is unmistakable: the assistant cannot satisfy it from memory-free small talk, and you can watch the tab actually navigate. If the answer comes back as 2018 and you saw your browser move, the connector is wired end to end. If the assistant answers 2018 without your browser doing anything, it answered from its own knowledge — ask it again and require it to cite the page it opened.

Quick answers

Can Claude control my browser from claude.ai, not just Claude Desktop?: Yes, via a custom connector. Claude Desktop can launch a local MCP server, but claude.ai, Cowork, and mobile cannot — they need a remote MCP server reachable over the public internet. The Vibe relay is exactly that, so one connector URL covers every Claude surface.
How do I add a custom connector in Claude?: Open Settings → Connectors, click Add, then Add custom connector. Give it a name, paste https://relay.api.vibebrowser.app/mcp/ followed by your routing UUID, and click Add. Then in a chat use the + button → Connectors and toggle it on for that conversation.
Claude says "You are not connected to Vibe Browser yet" — did it fail?: No. Claude reports a custom connector as not connected until the first time a conversation actually calls one of its tools. Send a prompt that requires the browser — for example asking it to open a page — and the status resolves. If tool calls then fail, see the troubleshooting table.
Do I need to verify a domain or get allowlisted?: No. Claude needs no domain verification and no allowlist request for a custom connector, and there is no consent screen to approve — you paste the connector URL and that is the whole setup.

Ready to connect Claude (web, Cowork & mobile)?

Install the extension All integrations

Setup steps

1Install the Vibe extension in Chrome

2Add the connector in Claude: Settings → Connectors → Add

3Turn it on in a chat

Check it works

Quick answers

Ready to connect Claude (web, Cowork & mobile)?