Chrome connection failures now point you to restarting with…

Chrome connection failures now point you to restarting with claude --chrome

If the Chrome extension is installed but the connection fails, Claude now suggests restarting with claude --chrome, adding --resume to continue

Use it nowTier: how much it should matter to you

2Useful: my rating, 1 to 5

1Signal: worth watching, 1 to 5

ChromeArea: what it touches

ImprovementsKind: in v2.1.323, 12 Nov 26

What probably matters to youSection of the release

What

Claude in Chrome lets Claude Code control your Chrome browser through an extension. Sometimes the extension is installed but the connection to the browser fails. Claude used to tell you to finish connecting with /chrome and its Reconnect extension option. It now tells you to restart Claude Code with claude --chrome. Add --resume to that command to pick the same conversation back up.

Why

The advice Claude gives you to recover from a failed browser connection is different now.

Read from

Names in the bundleclaude --chrome--resume

How sure we are

One source agreesOne thing we can check says the same as this entry.

Anthropic's release notes agreeFixed an interactive --chrome session giving no reason for starting without Claude in Chrome when your organization's policy turns it off: a…

See this entry in the whole of v2.1.323 →

The build it came inv2.1.323

12 Nov 2026 · 888 entries, this one is #102.

Use it now77
You'll notice533
Nothing to try yet64
Under the hood214

Either side of it

v2.1.322Older

Open the release →

Names in this entry

cli--chrome
Enable Chrome browser integration for web automation and testing
cli--resume
Resume a specific session by ID or name, or show an interactive picker to choose a session. In place of an ID, you can pass the absolute path to a session's .jsonl transcript file. The picker and name search include sessions that added this directory with /add-dir. When you pass a session ID, Claude Code searches the current project directory and its git worktrees, then every other project on this machine. Before v2.1.223, the ID search covered only the current project directory and its git worktrees. Background sessions appear in the picker marked with bg. Resuming one that is still running opens that session in this terminal through claude attach, and a prompt you pass on the command line goes to it as its next turn. Before v2.1.285, Claude Code refused and printed the claude attach command to run instead
slash/chrome
Configure Claude in Chrome settings

Anthropic's notes

Upstream's own release notes for v2.1.323 name something this entry names, so the two are probably about the same change. Probably: the pairing is made on a shared name rather than on the words around it.

Fixed an interactive --chrome session giving no reason for starting without Claude in Chrome when your organization's policy turns it off: a line now says so
Fixed Claude in Chrome setup saying /chrome finishes the connection; it now tells you to restart with claude --chrome
Changed claude rm and the agents view to say a session is removed from the list, not deleted; claude rm help says the conversation is kept and claude --resume lists it

Is this right?

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

v2.1.290 Claude stops trying Chrome tools when the browser connection has failed