{"version":"2.1.319","anchor":"chrome-tool-gating-now-keyed-on-tengu-copper-thimble-fallba","canonical_anchor":"chrome-tool-gating-now-keyed-on-tengu-copper-thimble-fallba","heading":"Staged change to how Claude Code recognises Chrome tools","tier":"soon","area":"Claude in Chrome","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/chrome-tool-gating-now-keyed-on-tengu-copper-thimble-fallba","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Staged change to how Claude Code recognises Chrome tools\n\nA new remote switch controls how Chrome browser tools are recognised; with it off, the old behaviour stays in place\n\n**Unclear.** What Claude Code does differently with Chrome tools once the switch is on is not clear.\n\n**What**\n\nClaude Code has a check that decides which tools belong to its Chrome browser integration. That check is now tied to a switch the server can turn on. It is off unless it is switched on remotely, and while it is off the check behaves as before. The check can also refresh the list of tools and, when the refreshed tools match, add extra text to the message it builds.\n\nAt the last reading this switch was off for this site's account and for an anonymous account.\n\n**Why**\n\nThis is a change prepared in advance. By default nothing differs for Chrome tool users.\n\n- Flag `tengu_copper_thimble`: Off in both readings (read for one account on one subscription tier against v2.1.319; this account: off, anonymous baseline: off, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Claude in Chrome\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}