### Preflight Checklist - [x] I have searched [existing issues](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20state%3Aopen%20label%3Abug) 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? Couldn't list connected browsers: JSON Parse error: Unexpected identifier "Browser" I've tried everything and same issues. ### What Should Happen? shou

[BUG] Couldn't list connected browsers: JSON Parse error: Unexpected identifier "Browser" Mac

Status Open

Maintainer reply None cached

Activity 7 comments · opened Jun 22, 2026

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?

Couldn't list connected browsers: JSON Parse error: Unexpected identifier "Browser" I've tried everything and same issues.

What Should Happen?

should connect and allow mcp

Error Messages/Logs

Couldn't list connected browsers: JSON Parse error: Unexpected identifier "Browser"

Steps to Reproduce

The browser extension is still not connected. The error from the /chrome command (JSON Parse error: ... "Browser")
confirms the bridge can't reach a running extension.

Let's get it connected. Please work through these in order:

Confirm the extension is installed — open chrome://extensions in Chrome and look for the Claude extension. If it's

not there, install it from https://claude.ai/chrome.

Confirm it's enabled — make sure its toggle is on (not greyed out), and that you're not in an Incognito window

where it's disabled.

Log into claude.ai in Chrome with the same account as Claude Code — chaseprogression@gmail.com. A mismatched

account is the most common cause.

Fully restart Chrome — quit completely (Cmd+Q, not just close the window) and reopen. First-time installs usually

don't register until a full restart.

After that, type /chrome again (or just tell me) and I'll re-check the connection.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

1.14271.0 (c8f4d8)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

7 Comments

github-actions[bot] · 2 months ago

Found 3 possible duplicate issues:

This issue will be automatically closed as a duplicate in 3 days.

If your issue is a duplicate, please close it and 👍 the existing issue instead
To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

Chaseprogression · 2 months ago

👎

rprwhite · 2 months ago

I'm also experiencing this issue, it's isolated to claude-code. Using Claude Desktop, Chrome is controlled as expected.

Chaseprogression · 2 months ago

Yes I've tried everything.
I see some other reports of this as being resolved. However, I don't believe that is the case.

calebcwells · 1 month ago

Also reproduces on Linux — so this isn't macOS-only (the platform:macos label may want broadening to include Linux).

Environment

Fedora Linux 43 (kernel 7.0.11), native (not WSL)
Claude Code 2.1.199
Google Chrome 149.0.7827.102 (native /usr/bin/google-chrome, not Chromium/Brave/Arc)
Extension "Claude" v1.0.79 (fcoeoabgfenejglbffodgkkbkcdhcgfn), same claude.ai account as Claude Code

Everything static is verified correct

NMH manifest present + correct at ~/.config/google-chrome/NativeMessagingHosts/com.anthropic.claude_code_browser_extension.json (allowed_origins = the installed extension id)
Wrapper ~/.claude/chrome/chrome-native-host executable, execs …/@anthropic-ai/claude-code/bin/claude.exe --chrome-native-host (exists)
After a full Chrome restart the bridge process does spawn: pgrep -af chrome-native-host → claude.exe --chrome-native-host, parent /opt/google/chrome/chrome
/chrome shows Status: Enabled, Extension: Installed, Enabled by default: Yes

Failure (identical to this issue)

/chrome → Select browser… (and the list_connected_browsers MCP tool) → Couldn't list connected browsers: JSON Parse error: Unexpected identifier "Browser" after a few seconds. The "Browser" token looks like the plain string "Browser extension is not connected…" leaking into the length-prefixed-JSON native-messaging stream instead of a JSON payload.
/chrome → Reconnect extension opens a tab that immediately closes; the parse error then recurs deterministically.

So on Linux too: the bridge starts and the process runs, but the browser-list response is not valid JSON. Config space is exhausted (manifest/host/versions/account/full-restart all correct). Looks like the same root cause as #64676 (native host spawns but never attaches).

iahu · 1 month ago

open Claude extension service worker on Chrome extension manage page, and then see if there are some webSocket connection errors WebSocket connection to 'wss://bridge.claudeusercontent.com/chrome/58d877e3-8399-4773-a75b-7e5ec52f06df' failed: Error in connection establishment: net::ERR_CONNECTION_CLOSED on the console panel, if so, make sure your network can connect to bridge.claudeusercontent.com.

Chaseprogression · 1 month ago

Same issue. Has anyone found a solution?