What
When 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.
Why
A session started by Claude Code now follows the Chrome choice you made for the session that started it.
Names in the bundle--chrome--no-chrome
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up --no-chrome, on Claude Code changelog.
* Fixed `/tui` disconnecting Claude in Chrome in a session started with `--chrome`, and ignoring `--no-chrome`changelog see the edit
Confirmed since
Anthropic's documentation has since written up --chrome, on Claude Code changelog.
* Fixed `/tui` disconnecting Claude in Chrome in a session started with `--chrome`, and ignoring `--no-chrome`changelog see the edit
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up --chrome, on Claude Code changelog.
Anthropic's release notes agree
Fixed /tui disconnecting Claude in Chrome in a session started with --chrome, and ignoring --no-chrome