[BUG] Claude in Chrome bridge permanently rejects with 'Invalid token or user mismatch' — server-side stale state (v1.2.234)

Bug Description

Claude Desktop's "Claude in Chrome" MCP bridge permanently rejects WebSocket connections with Invalid token or user mismatch (code 1008). The bridge UUID 34393944-435a-4fc8-b08c-2f945e38af69 persists across all client-side remediation attempts, indicating server-side stale state that no local action can clear.

Environment

• OS: macOS (Apple Silicon), Darwin 25.4.0
• Claude Desktop: v1.2.234
• Chrome Extension: Claude in Chrome v1.0.66
• Plan: Max
• Auth: Same account on both Desktop and Chrome extension (verified)

Steps to Reproduce

1. Open Claude Desktop (Code mode)
2. Open Chrome with Claude in Chrome extension installed and logged in
3. Attempt to use Claude in Chrome MCP tools (e.g., tabs_context_mcp)
4. Bridge connection fails immediately with token error

Error Logs

From ~/Library/Logs/Claude/main.log:

[Claude in Chrome] Connecting to bridge: wss://bridge.claudeusercontent.com/chrome/34393944-435a-4fc8-b08c-2f945e38af69
[Claude in Chrome] WebSocket connected, sending connect message
[Claude in Chrome] Bridge error: Invalid token or user mismatch
[Claude in Chrome] Bridge connection closed (code: 1008, duration: 0ms)

From ~/Library/Logs/Claude/chrome-native-host.log:

Chrome native host starting (version 0.1.0)
Socket created successfully at: /tmp/claude-mcp-browser-bridge-hongzhi/81957.sock
Entering main message loop
Chrome disconnected (EOF received)  ← instant disconnect

What I've Tried (ALL failed)

1. ✅ Re-login on both Desktop and Chrome extension
2. ✅ Reinstall Chrome entirely (full wipe including ~/Library/Application Support/Google/Chrome/)
3. ✅ Reinstall Claude in Chrome extension
4. ✅ Toggle Enabled off/on in Desktop → Connectors → Claude in Chrome
5. ✅ Toggle "Block extension" / "Allow extension" in Desktop → Settings → Claude in Chrome
6. ✅ Quit and reopen both Desktop and Chrome (multiple times)
7. ✅ Disconnect/reconnect cycle (Desktop first, then Chrome — per #27055 resolution)
8. ✅ Verified nativeMessaging permission present in extension manifest
9. ✅ Verified native messaging host manifest exists at correct path

Key Observation

The bridge UUID 34393944-435a-4fc8-b08c-2f945e38af69 never changes across all remediation attempts. Even after full Chrome reinstall, Desktop re-login, and extension re-login, the server returns the same UUID and rejects the token. This is consistent with server-side stale state as described in #27055.

Request

Please investigate and reset the bridge state for this account on the server side, or provide a client-side mechanism to force a fresh bridge handshake.

Related Issues

• #27055 (same root cause — server-side stale bridge state)
• #25736 (same error on macOS)
• #32011 (two distinct root causes for same error)
• #24935 (canonical regression issue)