{"version":"2.1.260","anchor":"decoy-enable-claude-in-chrome-tool-live-only-in-a-specifi","canonical_anchor":"decoy-enable-claude-in-chrome-tool-live-only-in-a-specifi","heading":"Decoy \"enable claude-in-chrome\" tool, live only in a specific remote session profile","tier":"soon","area":"Chrome & Browser","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/decoy-enable-claude-in-chrome-tool-live-only-in-a-specifi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### Decoy \"enable claude-in-chrome\" tool, live only in a specific remote session profile\n\nA decoy tool tells the model browser tools already exist, only active in a specific remote session profile.\n\nA 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.\n\n- Area: Chrome & Browser\n- Names: `enable__mcp__claude-in-chrome`, `CCR_SESSION_PROFILE`\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}