Claude in Chrome Extension: Install and Connect It to Claude Code
Claude in Chrome, also called Claude for Chrome, connects to Claude Code via claude --chrome, /chrome, or @browser in VS Code. It needs a paid plan and /login.
On this page

To use Claude in Chrome with Claude Code, install the Claude in Chrome extension from the Chrome Web Store listing (it appears there simply as "Claude", and many people search for it as "Claude for Chrome"), sign in to it with the same claude.ai account you use in Claude Code, and keep Chrome open. Then connect from wherever you run Claude Code:
| Where you use Claude Code | How to connect | What "working" looks like |
|---|---|---|
| Terminal (CLI) | Start with claude --chrome, or type /chrome inside a session | /chrome shows "Status: Enabled" and "Extension: Installed" |
| VS Code extension | Type @browser before your request, or /chrome in the prompt box | Claude opens a new tab and permission cards appear in the chat panel |
| Claude desktop app | Settings → Connectors → Claude in Chrome → Configure, then switch it on | Claude in Chrome shows up in the chat's Connectors menu, where you turn it on per conversation |
Check eligibility before you debug anything. As of October 22, 2026, Anthropic's Use Claude Code with Chrome documentation requires extension version 1.0.36 or later, a direct Anthropic plan (Pro, Max, Team, or Enterprise), and a Claude Code session signed in with /login. An API key, a claude setup-token token, or Claude through Amazon Bedrock, Google Cloud's Agent Platform, or Microsoft Foundry keeps the integration switched off. It also doesn't run inside WSL.
What this route is actually for
Claude in Chrome gives Claude Code a real, signed-in browser. Claude opens its own tabs in your Chrome window, shares the login state of the sites you already use, and works where you can watch it. Claude Code can already edit files and run tests. With the extension connected, it can also see what your app renders, read console errors and DOM state, and click through a flow you just changed.
That makes it the right tool when the browser itself is why the job is hard: a bug that only shows up in the rendered page, an admin panel behind your login, or a web app with no API you can call. It is the wrong default when a connector, an API, or a local file already holds the answer. In the Claude desktop app, Claude follows the same order on its own: a connector first, then the shell, then Claude in Chrome for browser work, and full computer use only when nothing narrower fits (Claude Code desktop documentation).
The extension also works on its own, in a Chrome side panel that runs separately from Claude Code. The steps below are for connecting it to Claude Code. If you're comparing Anthropic's extension with OpenAI's browser agent, see ChatGPT in Chrome vs Claude in Chrome: Both Now Control Your Tabs.
Who can use Claude in Chrome with Claude Code: plan, login, browser, WSL
Each of these conditions decides the outcome before any connection troubleshooting matters.
| Your setup | Works with Claude Code? | Why |
|---|---|---|
Pro, Max, Team, or Enterprise plan, signed in with /login | Yes | The supported path in the Claude Code docs |
| Free claude.ai plan | No | The Claude in Chrome getting-started page lists paid plans only |
Claude Code signed in with an API key or a claude setup-token token | No, Chrome stays off even with --chrome | The extension can't authenticate with those credentials. Before Claude Code v2.1.216 such sessions could switch it on, then every connection failed with a 403 error |
| Claude only through Amazon Bedrock, Google Cloud's Agent Platform, or Microsoft Foundry | No | Not offered through third-party providers. You need a separate claude.ai account |
| Team or Enterprise organization where an admin turned it off | No | Claude Code follows the org's Claude in Chrome setting. --chrome, /chrome, and the browser tools disappear |
| Enterprise organization with HIPAA enabled | Off until an Owner enables it | Turned on in Organization settings → Claude in Chrome. The BAA doesn't cover data sent to third-party sites through the extension |
| Windows Subsystem for Linux (WSL) | No | Claude Code reports "Claude in Chrome is not supported in WSL at this time." |
Which browsers work: Chrome, Edge, Brave, and Arc
Anthropic's two official pages disagree here, so start from the safer statement. The Claude Code Chrome documentation says the integration works with Google Chrome and Microsoft Edge, and that Claude Code also detects the extension and sets up the connection in other Chromium-based browsers, including Brave, Arc, Vivaldi, and Opera. The extension's own getting-started page says Claude in Chrome is not supported on other Chromium-based browsers or on mobile devices.
Use Google Chrome as your baseline. Edge is listed in the Claude Code docs, with its own host-file locations, so it is a reasonable second attempt. Brave, Arc, Vivaldi, and Opera may connect, but the extension's help page doesn't support them, so a failure there isn't something Anthropic's extension support covers.
Running Claude Code in WSL
If Claude Code runs inside WSL, the Chrome integration is not available, and the message "Claude in Chrome is not supported in WSL at this time." is the expected result, not a setup error. Run Claude Code natively on Windows (or on macOS or Linux) on the same machine as Chrome. The Claude Code install guide covers the native Windows install.
Turn it on in 5 minutes

Setup has four steps: install the extension, keep Chrome open, connect from Claude Code, and run one small test. For the connection, use the subsection that matches where you run Claude Code.
Install the Claude in Chrome extension
- Open Google Chrome and go to the Claude listing in the Chrome Web Store.
- Click Add to Chrome.
- Sign in with your Claude account when prompted. Use the same account and, if you belong to several, the same organization that Claude Code uses.
- Pin it: click the puzzle-piece icon, then the pin next to "Claude".
- Grant the permissions it asks for.
Clicking the Claude icon in the toolbar opens the extension's side panel. You don't need the side panel for Claude Code, but opening it once confirms the extension is signed in. The install itself is free. Using it requires one of the paid plans above.
If Claude Code needs the browser before you install anything, it may prompt you instead. In an interactive session it shows "Claude wants to use your browser" with three choices: Install extension (opens the install page, waits, connects, and offers "Continue with browser tools"), Not now, and Don't ask again. Some managed organization policies suppress this prompt.
Connect from the terminal with claude --chrome or /chrome
Start a new session with the flag:
claude --chromeThe first launch shows a one-time dialog about site permissions. Press Enter. If you're already in a session, type:
/chromeThe /chrome panel is where you check the connection, manage permissions, reconnect the extension, and pick a browser when more than one is connected (Select browser…). The integration works when the panel shows "Status: Enabled" and "Extension: Installed".
To stop passing the flag every time, choose Enabled by default in /chrome. Every session then loads the browser tools, which uses more context. If that matters, leave it off and connect only when you need it. claude --no-chrome turns the integration off for one session. A repository's .claude/settings.json can't switch Chrome on for you; only --chrome, /chrome, or your own user settings can.
The first time you enable it, Claude Code writes a small native messaging host file that Chrome reads only at startup. If the extension isn't detected on that first try, quit Chrome completely and reopen it.
If the claude command itself is missing or outdated, the Claude Code install guide covers installing and updating the CLI.
Connect from VS Code with @browser
In the Claude Code extension for VS Code, start a request with @browser:
@browser open the dev server on port 3000 and check the console for errorsTyping /chrome in the prompt box opens a dialog with the extension status and an Enabled by default switch. That switch shares one setting with the CLI, so turning it on in either place turns it on in both. Permission prompts show up as cards in the chat panel, and a card for a new site also offers to allow that site (Claude Code for VS Code documentation).
Connect from the Claude desktop app
In Claude Desktop, click your initials in the lower-left corner, open Settings → Connectors, find Claude in Chrome, click Configure, and switch it on. Install the extension if you haven't. The connector then appears in the Connectors menu of each chat, but it is off by default, so turn it on in each conversation where you want browser access.
In the desktop app's Code tab, Claude Code uses Claude in Chrome automatically for browser work once the extension is set up. If you're still deciding between the desktop app and the terminal, see Claude Code Desktop vs Terminal: Same Engine, Different Features.
Test it once before real work
Run a small task you can verify by eye:
Open the dev server on port 3000, submit the signup form with an invalid email, and tell me which error message appears and what the console logs.A working setup opens a new tab in a Chrome tab group for your session, asks for permission on that site, and reports back. If the first browser action asks to choose a browser, more than one is connected; pick the one you just set up. Typing /clear later closes that tab group.
One example from October 22, 2026, on a single Mac: Claude Code 2.1.307 in the Claude desktop app's Code tab drove Chrome through extension version 1.0.101, opened its own tab group, and read pages in the already signed-in Chrome profile. That check did not cover the terminal /chrome panel, VS Code, Edge, Brave, Arc, Windows, or WSL.
Claude in Chrome or the desktop app's built-in Browser pane
The Claude desktop app now has a second option. Its Code tab includes a built-in Browser pane (Cmd+Shift+B on macOS, Ctrl+Shift+B on Windows) where Claude can start your dev server, preview it, and check its own changes after each edit. That pane uses a clean browser profile with none of your saved logins or history (Claude Code desktop documentation).
| Choose | When |
|---|---|
| Claude in Chrome extension | Claude must act as you: sites you're signed in to, internal dashboards, Google Docs or Gmail, or a session from your Chrome profile |
| Desktop Browser pane | Building and testing your own app, or sites that don't need your identity. Nothing to install, and it doesn't touch your tabs |
Anthropic's desktop docs say it directly: when Claude should act as you in your logged-in sessions, use the Claude in Chrome extension. The Browser pane asks per site (Allow once, Always allow, Deny), but your local dev servers and project files need no approval. It follows the same allowlists and blocklists as the extension. It isn't available in SSH sessions. Cowork has its own built-in browser too, and you choose between it and Claude in Chrome under Settings → Cowork → Preferred browser (Claude Cowork built-in browser help page).
Best jobs for Claude in Chrome from Claude Code
Use the extension when the browser holds the truth you need. The Claude Code docs list these jobs, and they group into four kinds of work.
Testing and debugging your own app. Claude reads console errors and DOM state, then fixes the code that caused them. It can test form validation, check user flows after a change, or compare a page you built with a Figma mock. Ask for specific console patterns rather than the whole log, since logs get long.
Working in sites you're signed in to. Because Claude shares your login state, it can draft in Google Docs, work through Gmail or Notion, or read an admin panel without any API setup. This is the main reason to choose the extension over the desktop Browser pane.
Extracting data. Claude can pull names, prices, or table rows from pages and save them as a CSV or other local file, or collect information across several tabs.
Repetitive browser tasks. Data entry from a local spreadsheet into a web form, multi-site lookups, and file uploads all work. A single upload can include up to 10 MB of files. Claude refuses files with multiple hard links (common inside node_modules), and from Claude Code v2.1.293 it refuses credential files such as .env, .pem, .key, or anything under .ssh.
Claude can also record a GIF of a flow or save a screenshot to disk. A GIF captures everything visible, including account details on logged-in pages, so review it before sharing. For the full tool list, run /mcp, select claude-in-chrome, then View tools.
Skip the browser when a cleaner interface exists. A connector, an API, or a build artifact is faster and more reliable than clicking through a UI that wraps them. Browser work also counts against the same plan limits as Claude and Claude Code, and it uses more of them than ordinary chats (Claude in Chrome troubleshooting page).
Permissions, safety, and when to stay hands-on

Claude in Chrome acts inside your real browser, so its permissions work on two layers.
Claude Code's own prompts. Before a browser action, Claude Code asks first, with a dialog that starts "Claude in Chrome wants to" and an option to allow all actions on that site for the session. Since v2.1.251, browser actions always go through Claude Code's permission checks. In plan mode, Claude also asks before it records a GIF, opens a new tab, or runs a shortcut. In Claude Code's auto mode, when the auto-mode classifier approves a browser call, the extension skips its own per-site check for that call unless your permission rules deny the site. If you'd rather review each site yourself, stay out of auto mode for browser work.
The extension's site permissions. Claude Code inherits the site permissions you set in the extension. When Claude reaches a site that needs approval, a "New permissions required" prompt offers "Allow this action", "Always allow actions on this site", or "Decline" (Claude in Chrome permissions guide). Use "Always allow" only for sites you fully trust.
The three Claude in Chrome permission modes
When you use the extension from its side panel or from Claude Desktop, a drop-down on the chat input sets the mode:
| Mode | Former name | What happens |
|---|---|---|
| Manually approve | Ask before acting | Claude asks before each action. In the classic side panel it first shows a plan listing the sites it will visit |
| Automatically approve | (new) | Claude keeps working, screens each action for safety, blocks unsafe ones, and pauses when it needs you. Default in the Cowork side panel. Uses more of your usage limit |
| Skip all approvals | Act without asking | Nothing pauses and nothing checks actions automatically. Only for tasks where you trust every site, file, and connector involved |
In every mode, Claude still asks before it changes permission settings, grants authorizations, or enters potentially sensitive information, and it asks before downloads even on an "always allow" site. Some actions are off-limits regardless: purchases and financial transactions, creating accounts, handling card or ID data, downloads from untrusted sources, permanent deletions, investment advice or trades, modifying system files, and following instructions found in emails or web pages.
Where Claude in Chrome settings and site permissions live
- Approved sites: click the Claude icon, then the three dots in the side panel, then Extension settings. The Permissions page lists "Your approved sites", lets you revoke each one, and shows your permission history.
- Claude Code connection:
/chromein the terminal or in VS Code. - Claude Desktop connector: Settings → Connectors → Claude in Chrome.
- Team and Enterprise: admins can turn the extension off and set site allowlists and blocklists. If a site won't open for Claude, your organization may have blocked it.
Prompt injection and sensitive sites
The main risk is prompt injection: instructions hidden in a page, email, or document that try to redirect Claude. Two classifiers screen incoming content and each planned action. Anthropic says that, in its internal testing, Claude Opus 4.8 in the current configuration brings attack success below 0.08%, and adds that the risk is still not zero (Use Claude in Chrome safely).
Claude also takes screenshots of the tabs it works in, and it can't filter sensitive content out of them. Practical rules that follow from Anthropic's guidance:
- Use a separate Chrome profile without your banking, healthcare, or government accounts.
- Start with sites you trust, and avoid pages full of content from unknown users.
- Review proposed actions, especially on a site Claude hasn't visited before.
- Stop the task if Claude drifts off topic, opens sites you didn't expect, or asks for sensitive information.
Claude can't open adult or known pirated-content sites, and it asks first on financial sites. The default blocked categories also include banking, investment platforms, and crypto exchanges. You remain responsible for whatever Claude does in your browser, including messages sent and data changed.
If it does not connect or pauses unexpectedly
Run /chrome first and read the Status line. Then match the message you see:
| Message or symptom | Likely cause | Fix |
|---|---|---|
| "Browser extension is not connected" | Extension not installed or not running, signed in to a different claude.ai account or organization, or an org IP allowlist blocks bridge.claudeusercontent.com | Sign the extension in to the same account and organization, restart Chrome and Claude Code, then reconnect with /chrome |
"Not detected" in /chrome | Extension missing or disabled | Install or enable it in chrome://extensions |
| "No browsers are connected" | Chrome isn't open with the extension signed in to the same account and organization, or Claude Code can't reach bridge.claudeusercontent.com | Open Chrome, check the sign-in, then check network access to that host |
| "Receiving end does not exist" | The extension's service worker went idle | /chrome → "Reconnect extension" |
| "No tab available" | Claude acted before a tab was ready | Ask Claude to open a new tab and retry |
| Status reads "Not connected" after a long session | Idle service worker broke the connection | "Reconnect extension". Before v2.1.290 this only opened a page, so update Claude Code |
| "Claude Code ignored CLAUDE_CODE_ENABLE_CFC in this project's settings" | The project's settings tried to turn Chrome on | Start with claude --chrome or use Enabled by default in /chrome |
| "Claude in Chrome is not supported in WSL at this time." | Claude Code runs in WSL | Run Claude Code natively on the host OS |
| Commands stop responding on one page | A JavaScript alert, confirm, or prompt dialog is blocking the page | Dismiss the dialog yourself, then tell Claude to continue |
Extension installed but still not detected
Work through the Claude Code Chrome troubleshooting steps in this order:
- Confirm the extension is enabled in
chrome://extensions. - Run
claude --versionand update if you're behind. - Make sure Chrome is running.
- Run
/chromeand select "Reconnect extension". - Restart both Chrome and Claude Code.
If it still fails, check that the native messaging host file exists:
- macOS, Chrome:
~/Library/Application Support/Google/Chrome/NativeMessagingHosts/com.anthropic.claude_code_browser_extension.json - macOS, Edge:
~/Library/Application Support/Microsoft Edge/NativeMessagingHosts/com.anthropic.claude_code_browser_extension.json - Linux: the same file name under
~/.config/google-chrome/NativeMessagingHosts/or~/.config/microsoft-edge/NativeMessagingHosts/ - Windows: the registry key
HKCU\Software\Google\Chrome\NativeMessagingHosts\(Edge:HKCU\Software\Microsoft\Edge\NativeMessagingHosts\)
On a Mac that also runs Claude Desktop, a second file, com.anthropic.claude_browser_extension.json, belongs to the desktop app. Having both is normal. On the Mac described earlier, the Claude Code host file also sat in Edge and Brave folders even though neither browser was installed, so a host file alone doesn't show that a browser is supported.
Signed in to a different organization
If you belong to more than one claude.ai organization, the extension must use the same one as Claude Code, or the browser tools return "Browser extension is not connected" even with the same account. Run /status and read the Organization row. To switch, log out of the extension and log back in to that organization. Logging out deletes the shortcuts and scheduled tasks saved in the extension, so try the other fixes first.
Windows-specific problems
- EADDRINUSE (named pipe conflict): another Claude Code session is using the pipe. Close other sessions that use Chrome and restart Claude Code.
- Native host crashes on startup: reinstall Claude Code to regenerate the host configuration.
- Setup page never opens: update Claude Code. Versions before v2.1.211 could fail to open it on Windows.
When Claude pauses on a login page or CAPTCHA
That pause is by design. When Claude reaches a login page or a CAPTCHA, it stops and asks you to handle it in the visible Chrome window, then continues. Do that step yourself. Don't look for ways to make Claude get past it; Anthropic's safety page lists bypassing CAPTCHAs among the things Claude won't do.
FAQ
Does Claude in Chrome replace full computer use?
No. Claude in Chrome controls only the browser, with your logged-in sessions and site permissions. Computer use controls native apps through the screen, and in the desktop app it comes last, after connectors, the shell, and Claude in Chrome. Use the extension for browser jobs. For desktop control across the API, Cowork, and Claude Code, see Claude Computer Use in 2026: API Tool vs Cowork vs Claude Code.
Which plan and model do I need?
A paid plan: Pro, Max, Team, or Enterprise. For Claude Code, the session must also be signed in with /login through that plan, not an API key, a claude setup-token token, or a cloud provider such as Bedrock. Anthropic's getting-started page says Claude in Chrome is available on all public models, so there is no separate model requirement. On Team and Enterprise, an admin must have the extension enabled for your organization.
Is Claude in Chrome free?
Installing it is free, but it only works with a paid Claude plan. Browser tasks count against the same usage limits as Claude and Claude Code, and they use more of those limits than regular chats. The "Automatically approve" mode uses still more because of its extra safety checks.
Does it work in Microsoft Edge?
According to the Claude Code docs, yes: the integration lists Google Chrome and Microsoft Edge, and documents Edge's host-file locations. The extension's own help page says it isn't supported on other Chromium-based browsers. Set it up in Google Chrome first. Try Edge second, and treat Brave, Arc, Vivaldi, and Opera as possible but unsupported by the extension's help page.
Why does Chrome say Claude started debugging this browser?
Claude in Chrome uses Chrome's debugger permission to click, type, and take screenshots. Whenever an extension attaches through that permission, Chrome shows a bar at the top of the window saying the extension started debugging the browser. It means Claude is controlling the tab. Leave it visible; if you didn't expect Claude to be working, stop the task.
Why does Claude stop and wait during login or CAPTCHA?
Because those steps are reserved for you. Claude in Chrome shares your browser session but pauses at login pages and CAPTCHAs, asks you to complete them in the visible window, and then continues the task.
Should I use this on sensitive sites?
Anthropic advises against it. Claude takes screenshots of the tabs it works in and can't filter out sensitive data, and prompt injection risk is reduced but not zero. Keep financial accounts, medical information, legal documents, and other people's personal data out of it, and use a separate Chrome profile for browser work.
Sources9
External pages this guide links to, in the order they appear. Last updated Oct 22, 2026.
Sources9
External pages this guide links to, in the order they appear. Last updated Oct 22, 2026.
- 1.Chrome Web Store listingchromewebstore.google.com/detail/claude/fcoeoabgfenejglbffodgkkbkcdhcgfn
- 2.Use Claude Code with Chrome documentationcode.claude.com/docs/en/chrome
- 3.Claude Code desktop documentationcode.claude.com/docs/en/desktop
- 4.Claude in Chrome getting-started pagesupport.claude.com/en/articles/12012173-get-started-with-claude-in-chrome
- 5.Claude Code for VS Code documentationcode.claude.com/docs/en/vs-code
- 6.Claude Cowork built-in browser help pagesupport.claude.com/en/articles/16607400-use-the-built-in-browser-in-claude-cowork
- 7.Claude in Chrome troubleshooting pagesupport.claude.com/en/articles/12902405-claude-in-chrome-troubleshooting
- 8.Claude in Chrome permissions guidesupport.claude.com/en/articles/12902446-claude-in-chrome-permissions-guide
- 9.Use Claude in Chrome safelysupport.claude.com/en/articles/12902428-use-claude-in-chrome-safely





