{"version":"2.1.293","anchor":"spawned-sessions-now-forward-chrome-no-chrome","canonical_anchor":"spawned-sessions-now-forward-chrome-no-chrome","heading":"Sessions started by Claude Code now keep your Chrome on or off choice","tier":"notice","area":"Chrome","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/spawned-sessions-now-forward-chrome-no-chrome","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Sessions started by Claude Code now keep your Chrome on or off choice\n\nSessions that Claude Code starts on its own now pass along `--chrome` or `--no-chrome` when the Chrome setting was set either way\n\n**What**\n\nWhen Claude Code starts another session of its own, it now passes on your Chrome browser integration choice. This is the feature that lets Claude use Chrome for web tasks. If Chrome was explicitly turned on, the new session gets `--chrome`. If it was explicitly turned off, it gets `--no-chrome`. If you never decided either way, nothing is passed. Before, no Chrome flag was passed to these sessions.\n\n**Why**\n\nA session started by Claude Code now follows the Chrome choice you made for the session that started it.\n\n- Area: Chrome\n- Names: `--chrome`, `--no-chrome`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}