Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.260 ·

Decoy "enable claude-in-chrome" tool, live only in a specific remote session profile

A decoy tool tells the model browser tools already exist, only active in a specific remote session profile.

TierNothing to try yethow much it should matter to you
Useful2my rating, 1 to 5
Signal3worth watching, 1 to 5
AreaChrome & Browserwhat it touches
KindIn Developmentin v2.1.260,
Nothing to try yet Notable No documentation found

A decoy tool tells the model browser tools already exist, only active in a specific remote session profile.

A new tool, enable__mcp__claude-in-chrome (with a generic Browser variant), does nothing but tell the model that browser tools are already available under names containing Claude_Browser, or to use claude-in-chrome/Claude_in_Chrome tools directly, so the model stops trying to invoke a non-existent "enable" step. It only registers when the session runs under a CCR session profile, requiring CCR_SESSION_PROFILE, a valid SESSION_INGRESS_URL, a CLAUDE_CODE_REMOTE_SESSION_ID matching the cse_... pattern, and a first-party check; outside that remote/cloud profile the tool is not registered at all.

Read from
Names in the bundleenable__mcp__claude-in-chromeCCR_SESSION_PROFILE

See this entry in the whole of v2.1.260 →

Feedback