[BUG] Browser extension connection broken in v2.1.25 - works in v2.1.19
Bug Description
The Claude browser extension (claude-in-chrome) fails to connect when using Claude Code version 2.1.25. The same extension works perfectly when downgrading to version 2.1.19.
Steps to Reproduce
- Install Claude Code v2.1.25 (latest via
claude update) - Ensure the Claude browser extension is installed and enabled in Chrome
- Try to use any browser automation tool (e.g.,
tabs_context_mcp) - Receive error: "Browser extension is not connected"
Expected Behavior
The browser extension should connect and respond to MCP tool calls, as it does in version 2.1.19.
Actual Behavior
Error message: "Browser extension is not connected. Please ensure the Claude browser extension is installed and running..."
Workaround
Downgrade to version 2.1.19:
npm install -g @anthropic-ai/claude-code@2.1.19
Environment
- Claude Code version (broken): 2.1.25
- Claude Code version (working): 2.1.19
- OS: Windows 11
- Browser: Chrome (latest)
- Extension: Claude browser extension (installed and enabled)
Priority
This is a critical regression that breaks all browser automation functionality. Please prioritize fixing this issue.
Additional Context
The extension is definitely installed and running - it works immediately after downgrading to 2.1.19 without any other changes. This suggests a breaking change was introduced between 2.1.19 and 2.1.25.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗