[BUG] /chrome cannot enable Chrome in an existing session — docs say it can

Description

The documentation states that Chrome can be enabled from within an existing session:

"You can also enable Chrome from within an existing session by running /chrome." — https://code.claude.com/docs/en/chrome

On v2.1.210 (macOS) this is not possible. A session started without --chrome shows Status: Disabled, and the /chrome panel exposes no action to enable it for the current session.

Steps to reproduce

1. Start a session without the flag: claude
2. Run /chrome → Status: Disabled, Extension: Installed (green)
3. Panel offers only: Manage permissions, Reconnect extension, Enabled by default: No
4. Set Enabled by default to Yes
5. Run /chrome again → Enabled by default: Yes and Status: Disabled at the same time
6. Reconnect extension does nothing

Expected

Either /chrome enables the integration for the current session as documented, or the panel and the docs state clearly that a restart is required.

Actual

No way to enable Chrome in a running session. The only working path is to exit and relaunch with claude --chrome (or claude --continue --chrome, which preserves the conversation).

Why this costs hours

1. Status: Disabled is ambiguous. It means both "not enabled for this session" and "broken / cannot connect", with nothing to tell them apart. I spent two days believing the integration was broken when it was simply off.
2. "Reconnect extension" is a dead end. It is offered while the integration is off for the session, where it cannot do anything, and it reports nothing back. It reads as the obvious remedy, so that is where you keep going.

Setting Enabled by default to Yes and seeing Status: Disabled on the very next line is the clearest illustration of the problem.

Environment

• Claude Code 2.1.210, macOS (Darwin 25.5.0, Apple Silicon)
• Chrome extension installed, shown Installed (green) throughout
• Native messaging manifest and host verified correct (manifest → wrapper script → ~/.local/bin/claude symlink → current version)

Not a duplicate of #33758

That issue (--chrome ignored on --resume, closed) is a different one: claude --continue --chrome works correctly on 2.1.210. This report is about enabling from within a running session, which the docs promise and the build does not deliver.