Use Claude Code with Chrome changedchrome
Nearest release: v2.1.305, published an hour after upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 20 Oct 2026 18:25 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 20 Oct 2026 18:37 UTC.
Upstream edited
Recorded here
Lines+35added
Lines−36removed
From line
11
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits20to this page, all time
The whole hunk
from line 11, old and new numbered
/
from line 11
1111* When you type `/clear`, Claude Code closes the group, open pages included, unless work that survives the clear is still running
1212* When you switch sessions with a command like `/resume`, exit Claude Code, or run a `/clear` while work that survives it is still running, Claude Code closes the group only if it holds nothing but empty new tabs, so pages you may still be reading stay open
1313
14<Note>
15 Chrome integration works with Google Chrome and Microsoft Edge. Claude Code also detects the extension and sets up the connection in other Chromium-based browsers, including Brave, Arc, Vivaldi, and Opera. Chrome integration isn't supported in Windows Subsystem for Linux (WSL).
16</Note>
14> [!NOTE]
15>
16> Chrome integration works with Google Chrome and Microsoft Edge. Claude Code also detects the extension and sets up the connection in other Chromium-based browsers, including Brave, Arc, Vivaldi, and Opera. Chrome integration isn't supported in Windows Subsystem for Linux (WSL).
1717
1818## Capabilities
1919
from line 41
4141
4242Chrome integration also requires signing in with `/login`. If you authenticate with an API key or a long-lived token from [`claude setup-token`](/docs/en/authentication#generate-a-long-lived-token), Claude Code keeps Chrome integration off, even when you pass `--chrome`, because the browser extension can't authenticate with those credentials. Before v2.1.216, these sessions could enable Chrome integration, but every attempt to connect to the browser extension failed with a 403 error.
4343
44<Note>
45 Chrome integration is not available through third-party providers like Amazon Bedrock, Google Cloud's Agent Platform, or Microsoft Foundry. If you access Claude exclusively through a third-party provider, you need a separate claude.ai account to use this feature.
46</Note>
44> [!NOTE]
45>
46> Chrome integration is not available through third-party providers like Amazon Bedrock, Google Cloud's Agent Platform, or Microsoft Foundry. If you access Claude exclusively through a third-party provider, you need a separate claude.ai account to use this feature.
4747
4848## Get started in the CLI
4949
50<Steps>
51 <Step title="Launch Claude Code with Chrome">
52 Start Claude Code with the `--chrome` flag:
50**1. Launch Claude Code with Chrome**
5351
54 ```bash theme={null}
55 claude --chrome
56 ```
52Start Claude Code with the `--chrome` flag:
5753
58 The first time you launch with Chrome, Claude Code shows a one-time dialog that introduces the integration and explains how site permissions work. Press Enter to continue.
54```bash theme={null}
55claude --chrome
56```
5957
60 To enable Chrome for future sessions without the flag, see [Enable Chrome by default](#enable-chrome-by-default).
61 </Step>
58The first time you launch with Chrome, Claude Code shows a one-time dialog that introduces the integration and explains how site permissions work. Press Enter to continue.
6259
63 <Step title="Ask Claude to use the browser">
64 This example navigates to a page, interacts with it, and reports what it finds, all from your terminal or editor:
60To enable Chrome for future sessions without the flag, see [Enable Chrome by default](#enable-chrome-by-default).
6561
66 ```text wrap theme={null}
67 Go to code.claude.com/docs, click on the search box,
68 type "hooks", and tell me what results appear
69 ```
62**2. Ask Claude to use the browser**
7063
71 If Claude Code asks for permission before a browser action, approve it. The dialog starts with `Claude in Chrome wants to` and offers an option to allow all actions on that site for the session. Claude opens a new tab and starts the task.
72 </Step>
73</Steps>
64This example navigates to a page, interacts with it, and reports what it finds, all from your terminal or editor:
7465
66```text wrap theme={null}
67Go to code.claude.com/docs, click on the search box,
68type "hooks", and tell me what results appear
69```
70
71If Claude Code asks for permission before a browser action, approve it. The dialog starts with `Claude in Chrome wants to` and offers an option to allow all actions on that site for the session. Claude opens a new tab and starts the task.
72
7573Run `/chrome` at any time to check the connection status, manage permissions, reconnect the extension, or choose which connected browser to use. The integration is working when the status panel shows "Status: Enabled" and "Extension: Installed".
7674
7775If more than one browser is connected, you choose which one Claude uses. When a browser action starts before you've chosen, Claude prompts you to pick one. To switch browsers later, run `/chrome` and select **Select browser…**. Claude keeps using your choice even when another browser connects.
from line 99
10199
102100Claude Code starts normally when Chrome isn't running.
103101
104<Note>
105 Enabling Chrome by default increases context usage since the browser tools and their instructions are always loaded. If you notice increased context consumption, turn the setting off and connect only when needed, with `--chrome` in the CLI or by typing [`@browser`](/docs/en/vs-code#automate-browser-tasks-with-chrome) in the VS Code prompt box.
106</Note>
102> [!NOTE]
103>
104> Enabling Chrome by default increases context usage since the browser tools and their instructions are always loaded. If you notice increased context consumption, turn the setting off and connect only when needed, with `--chrome` in the CLI or by typing [`@browser`](/docs/en/vs-code#automate-browser-tasks-with-chrome) in the VS Code prompt box.
107105
108106### Manage site permissions
109107
from line 301
303301
304302To see which organization Claude Code is signed in to, run [`/status`](/docs/en/commands) at the Claude Code prompt and read the `Organization` row.
305303
306<Warning>
307 If you log out of the extension, you lose the shortcuts and scheduled tasks saved in it. Try the other fixes under [Common error messages](#common-error-messages) first.
308</Warning>
304> [!WARNING]
305>
306> If you log out of the extension, you lose the shortcuts and scheduled tasks saved in it. Try the other fixes under [Common error messages](#common-error-messages) first.
309307
310308To change the extension's organization, log out in the extension's settings, then log in and select the organization that `/status` shows.
311309
from line 325
327325| Extension shows "Not detected" in `/chrome` | Chrome extension is not installed or is disabled | Install or enable the extension in `chrome://extensions` |
328326| "No tab available" | Claude tried to act before a tab was ready | Ask Claude to create a new tab and retry |
329327| "Receiving end does not exist" | Extension service worker went idle | Run `/chrome` and select "Reconnect extension" |
328| "No browsers are connected" | Chrome isn't open with the extension signed in to the same claude.ai account and organization as Claude Code, or Claude Code can't reach `bridge.claudeusercontent.com` | Confirm Chrome is open and the extension is signed in to the same claude.ai account and [organization](#extension-signed-in-to-a-different-organization) as Claude Code. If so, check that your network lets Claude Code reach `bridge.claudeusercontent.com`, listed under [Network access requirements](/docs/en/network-config#network-access-requirements) |
330329
331330## See also
332331
No line in this hunk matches that.