Built-in browser and Claude in Chrome changedthird-party/claude-desktop/browser
Nearest release: v2.1.310, published under an hour before 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 23 Oct 2026 22:00 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 23 Oct 2026 22:07 UTC.
Upstream edited
Recorded here
Lines+1added
Lines−1removed
From line
14
where the diff opens
First seen
17 Sep 2026
this site's first read of the page
Recorded edits11to this page, all time
The whole hunk
from line 14, old and new numbered
/
from line 14
1414
1515In **Organization settings** on claude.ai, open the **Claude in Chrome** page and turn on the **Enable for your team** switch. On the same page, choose whether Claude in Chrome works on every site except the ones you block, or only on the sites you allow. Then add sites with the **Add websites** button. These site permissions are the same ones the built-in browser uses for your organization.
1616
17Claude in Chrome also needs the **Allow user-added MCP servers** switch on the **Connectors** page under **Desktop 3P** in **Organization settings** to stay on. While that switch is off, Claude Desktop doesn't connect to Claude in Chrome.
17Claude in Chrome also needs the **Allow local MCP servers** switch on the **Connectors** page under **Desktop 3P** in **Organization settings** to stay on. While that switch is off, Claude Desktop doesn't connect to Claude in Chrome.
1818
1919### Set up Claude in Chrome on a device
2020
No line in this hunk matches that.