Chrome extension not connecting despite correct native messaging host configuration

Resolved 💬 3 comments Opened Feb 11, 2026 by verygreenboi Closed Feb 15, 2026

Environment:

  • Claude Code version: 2.1.15
  • macOS version: 26.2 (Build 25C56)
  • Chrome version: Version 144.0.7559.133 (Official Build) (arm64)
  • Extension ID: fcoeoabgfenejglbffodgkkbkcdhcgfn

Description:
The Chrome browser extension fails to connect to Claude Code. All configuration files appear correct, but tabs_context_mcp consistently returns "Browser extension is not connected."

Steps to Reproduce:

  1. Install the Claude browser extension from claude.ai/chrome.
  2. Restart Chrome
  3. Run the /chrome command or use any mcp__claude-in-chrome__* tool.
  4. Connection fails

Verified Configuration:

The native messaging host file exists at:
~/Library/Application Support/Google/Chrome/NativeMessagingHosts/com.anthropic.claude_code_browser_extension.json

Contents:
```json
{
"name": "com.anthropic.claude_code_browser_extension",
"description": "Claude Code Browser Extension Native Host",
"path": "/Users/xxx/.claude/chrome/chrome-native-host",
"type": "stdio",
"allowed_origins": [
"chrome-extension://fcoeoabgfenejglbffodgkkbkcdhcgfn/"
]
}


- The native host script exists and is executable at /Users/tom/.claude/chrome/chrome-native-host
- Script points to correct Claude binary at /Users/tom/.local/share/claude/versions/2.1.15
- Extension ID matches the allowed_origins in config                            
                                                                                                                                                                    
The service worker console shows no errors.
                                                                                  
**Expected Behavior**:
The Chrome extension should connect, and tabs_context_mcp should return tab information.
                                                                                  
**Actual Behavior**:
Always returns "Browser extension is not connected" even after multiple Chrome restarts.

View original on GitHub ↗

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