{"version":"2.1.290","anchor":"chrome-setup-offer-now-decided-by-the-host","canonical_anchor":"chrome-setup-offer-now-decided-by-the-host","heading":"The app running Claude Code now decides about the Chrome setup offer","tier":"notice","area":"Chrome & Browser","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/chrome-setup-offer-now-decided-by-the-host","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### The app running Claude Code now decides about the Chrome setup offer\n\nWhether the Chrome setup offer appears now depends on the app hosting Claude Code, not on SSH-related environment variables\n\n**Unclear.** It is not clear which apps declare that they show the offer themselves.\n\n**What**\n\nClaude Code can offer to set up its Chrome browser connection. Before, whether that offer was shown depended on Claude Code not running standalone, and on `SSH_AUTH_SOCK` and `GIT_SSH_COMMAND` not being set. Now it asks the host, the app Claude Code runs inside, whether the host shows the offer itself.\n\nApps that embed Claude Code through the SDK can declare this with `declareHostRendersChromeSetupOffer`. They can also declare `declareForwardNestedSubagentToolCalls`.\n\n**Why**\n\nThe decision now depends on the app you are using rather than on guesses from environment variables, so the offer may appear in different places than before.\n\n- Area: Chrome & Browser\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}