[BUG] No Chrome extension connected" error provides no guidance on how to reconnect

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

When the Claude in Chrome extension loses its connection (e.g., after closing/reopening
Chrome or starting a new Claude Code session), the error message provides no guidance
on how to fix it.

What Should Happen?

• Error shown: "No Chrome extension connected"
• The "Reconnect extension" button in the Claude Code UI does not work
• There is no indication that the user needs to manually visit the pairing page

Error Messages/Logs

- Error shown: `"No Chrome extension connected"`
  - The "Reconnect extension" button in the Claude Code UI does not work
  - There is no indication that the user needs to manually visit the pairing page

Steps to Reproduce

## Steps to reproduce

1. Complete initial Chrome extension pairing
2. Close and reopen Chrome
3. Start a new Claude Code session
4. Attempt any browser automation tool call
5. Observe error: "No Chrome extension connected"

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

v2.1.50

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

Other

Additional Information

• The pairing connection is session-based, not persistent — this is not documented anywhere
• On Linux with Flatpak Chrome, additional undocumented steps are required to make

native messaging work at all (filesystem overrides, manual NativeMessagingHosts setup)

• Users who complete initial setup have no way to know they need to re-pair on each session

• OS: Linux (Ubuntu/KDE Plasma)
• Chrome: Google Chrome via Flatpak (com.google.Chrome)
• Claude Code version: latest