[DOCS] Chrome docs do not explain account-mismatch failure mode fixed in v2.1.178

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/chrome

Section/Topic

Troubleshooting → "Common error messages" (and the surrounding Troubleshooting section)

Current Documentation

The chrome page lists these troubleshooting cases:

### Extension not detected If Claude Code's setup-issues line lists chrome: 1. Verify the Chrome extension is installed and enabled in chrome://extensions 2. Verify Claude Code is up to date by running claude --version 3. Check that Chrome is running 4. Run /chrome and select "Reconnect extension" to re-establish the connection 5. If the issue persists, restart both Claude Code and Chrome

### Common error messages | Error | Cause | Fix | |---|---|---| | "Browser extension is not connected" | Native messaging host cannot reach the extension | Restart Chrome and Claude Code, then run /chrome to reconnect | | "Extension not detected" | Chrome extension is not installed or is disabled | Install or enable the extension in chrome://extensions | | "No tab available" | Claude tried to act before a tab was ready | Ask Claude to create a new tab and retry | | "Receiving end does not exist" | Extension service worker went idle | Run /chrome and select "Reconnect extension" |

The page never mentions account identity. The only authentication-related note in the file is the Prerequisites block stating that "a direct Anthropic plan (Pro, Max, Team, or Enterprise)" is required, and a <Note> that Chrome integration is not available through Bedrock/Vertex/Foundry.

What's Wrong or Missing?

The v2.1.178 changelog records the following fix:

Fixed Claude in Chrome silently failing to connect when the OAuth token belongs to a different account than the Claude Code login

The docs do not acknowledge this scenario anywhere. The failure was silent before the fix, which means users with a Chrome extension signed in to account A and Claude Code logged in via account B would have seen the existing "Reconnect extension" / "Browser extension is not connected" guidance and would have been unable to resolve the issue, because the root cause was a token-identity mismatch, not the messaging host or extension lifecycle.

The chrome page troubleshooting section is the natural home for this case and currently has no entry that covers account identity. After the v2.1.178 fix, users who hit this should be able to find the cause and the resolution in the docs rather than only in the changelog.

Suggested Improvement

Add a new troubleshooting subsection and a new row to the "Common error messages" table on the chrome page. For example:

### Extension connects but actions fail or appear stuck If Claude in Chrome is detected but browser actions hang or never run, the Claude in Chrome extension may be signed in to a different account than Claude Code. Both sides must be authenticated to the same Claude account. Sign out of the extension in Chrome and run /login in Claude Code, or vice versa, so the same account is used on both sides.

And add a row to the Common error messages table:

| Connection appears successful but commands hang | Claude in Chrome is signed in to a different account than Claude Code | Sign out of the extension and re-authenticate both sides to the same Claude account |

A cross-reference to https://code.claude.com/docs/en/authentication would also help users who want to inspect which account is active.

Impact

High - Prevents users from using a feature

Additional Context

Affected Pages:
| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/chrome | Primary documentation location for Claude in Chrome troubleshooting |
| https://code.claude.com/docs/en/changelog | Source of the v2.1.178 fix bullet |

Total scope: 1 page affected (chrome.md).

Cross-references:

• https://code.claude.com/docs/en/authentication — describes which account is active for Claude Code.
• v2.1.178 changelog (docs/code.claude.com/docs/en/changelog.md, line 24): "Fixed Claude in Chrome silently failing to connect when the OAuth token belongs to a different account than the Claude Code login."