Chrome extension not connecting to native host (macOS 26.3)

Resolved 💬 3 comments Opened Apr 13, 2026 by jetsuthpring Closed Apr 16, 2026

***Bug Report
The Chrome extension (claude-in-chrome) fails to connect to the native messaging host. tabs_context_mcp always returns "Browser extension is not connected."
Environment
Claude Code version: 2.1.104
macOS: 26.3 (Build 25D125)
Chrome: 147.0.7727.56
Extension installed: Yes (from Chrome Web Store)
Native Host Config
~/Library/Application Support/Google/Chrome/NativeMessagingHosts/com.anthropic.claude_code_browser_extension.json exists and points to the correct binary: {
"name": "com.anthropic.claude_code_browser_extension",
"description": "Claude Code Browser Extension Native Host",
"path": "/Users/jet/.claude/chrome/chrome-native-host",
"type": "stdio",
"allowed_origins": [
"chrome-extension://fcoeoabgfenejglbffodgkkbkcdhcgfn/"
]
}
The wrapper script at ~/.claude/chrome/chrome-native-host correctly points to the installed binary, and the binary exists and is executable.
What I've tried
Restarting Chrome
Verifying the extension is installed and enabled
Confirming the native messaging host config and binary are in place and correct
Confirmed logged into claude.ai with the same account as Claude Code
Expected behavior
tabs_context_mcp should connect to Chrome and return tab context.
Actual behavior
Always returns: "Browser extension is not connected."

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗