{"version":"2.1.309","anchor":"chrome-bridge-phone-answer-branch-behind-tengu-glowing-panc","canonical_anchor":"chrome-bridge-phone-answer-branch-behind-tengu-glowing-panc","heading":"Different reply when Chrome is unreachable from a session on a phone","tier":"soon","area":"Browser","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/chrome-bridge-phone-answer-branch-behind-tengu-glowing-panc","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Different reply when Chrome is unreachable from a session on a phone\n\nWhen the Chrome extension is not connected, Claude Code can give a different reply to remote sessions on a phone, behind a switch that is off by default\n\n**Unclear.** What the different message says, and which devices the platform check matches, is not stated.\n\n**What**\n\nClaude Code can control Chrome through a browser extension. When that extension is not connected, Claude Code says so. A new step can now return a different message instead, when all of these hold:\n\n- the `tengu_glowing_pancake` switch is on; it is off unless it is switched on remotely\n\n- the session passes a check for being a remote session\n\n- the device used for the last turn passes a platform check\n\n**Why**\n\nIt changes what Claude tells you when you use a session from your phone and Chrome is out of reach.\n\n- Flag `tengu_glowing_pancake`: Not enough to say (read for one account on one subscription tier against v2.1.309; this account: no value returned, anonymous baseline: no value returned, 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: Browser\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}