{"version":"2.1.323","anchor":"chrome-setup-interruption-message-now-points-to-claude-ch","canonical_anchor":"chrome-setup-interruption-message-now-points-to-claude-ch","heading":"Claude in Chrome recovery advice now says to restart with claude --chrome","tier":"use","area":"Chrome","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/chrome-setup-interruption-message-now-points-to-claude-ch","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Claude in Chrome recovery advice now says to restart with claude --chrome\n\nInterrupted, declined or failed Claude in Chrome setups now tell you to restart with `claude --chrome` (and `--resume`) instead of using \/chrome\n\n**What**\n\nClaude in Chrome lets Claude control your Chrome browser through an extension. When setup does not finish, Claude Code used to say that `\/chrome` would complete the connection later, or that the next session would detect the extension. Every one of these messages now gives the same advice: restart Claude Code with `claude --chrome`, and add `--resume` to pick the same conversation back up. `--chrome` is the command-line option that turns on [Chrome browser integration](https:\/\/code.claude.com\/docs\/en\/chrome.md).\n\n- Interrupted setup: the message Claude receives now says the user can get browser tools by restarting with `claude --chrome`.\n\n- Declined extension install: the message no longer says `\/chrome` finishes the connection later, and points to `claude --chrome` instead.\n\n- Extension installed but browser tools off: Claude is told to have the user restart with `claude --chrome`. It previously said to run `\/chrome` or restart for a one-time prompt.\n\n- Bypass-permissions mode, where Claude acts without asking for approval: if browser tools could not be enabled, the message now says to restart with `claude --chrome`, leaving bypass permissions off.\n\n- \"Continue without browser tools\" option: its description now reads \"Add them later with claude --chrome\" instead of \"Finish setup later with \/chrome\".\n\n- Setup failure screen: it now reads \"Couldn't connect to the extension. To try again, restart Claude Code with claude --chrome --resume.\" When your Claude Code or organization settings block the feature, it instead says \"Your Claude Code or organization settings don't allow Claude in Chrome.\"\n\n- Failed state in the setup dialog: the only option offered is to skip. Other states keep their earlier options, including \"Keep waiting\".\n\n- A new window for returning from the browser during setup was also added.\n\n**Why**\n\nIf Chrome setup is cut short, Claude and the setup screens now point you to one consistent way to get browser tools back without losing your conversation. When the feature is blocked by policy, the failure screen says so instead of suggesting a retry that cannot work.\n\n- Area: Chrome\n- Names: `claude --chrome`, `--resume`\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}