{"version":"2.1.299","anchor":"chrome-permission-prompt-now-denies-up-front-when-no-browser","canonical_anchor":"chrome-permission-prompt-now-denies-up-front-when-no-browser","heading":"Claude in Chrome refuses a tool call at once when no browser is connected","tier":"notice","area":"Browser","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/chrome-permission-prompt-now-denies-up-front-when-no-browser","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Claude in Chrome refuses a tool call at once when no browser is connected\n\nClaude in Chrome tool calls are now denied straight away with 'no browser connected' when no browser extension is attached\n\n**What**\n\nClaude in Chrome lets Claude Code control your Chrome browser through a browser extension. Before showing the permission prompt for one of its actions, Claude Code now checks whether any browser with the extension is connected. It can only do this when it is able to list the connected extensions and knows this device's id.\n\nIf no browser is connected, the action is denied with the reason \"Claude in Chrome: no browser connected\".\n\nThe check is controlled by a remote setting that stays on unless it is switched off from the server.\n\n**Why**\n\nA Chrome action with no browser attached now fails right away with a clear reason, instead of asking you for permission or waiting until it times out.\n\n- Flag `tengu_hushed_lantern`: Not enough to say (read for one account on one subscription tier against v2.1.299; this account: no value returned, anonymous baseline: no value returned, compiled default: on) 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: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}