Chrome extension connection drops when returning to terminal after /chrome command
Resolved 💬 2 comments Opened Feb 2, 2026 by rancohen-pictime Closed Mar 3, 2026
## Description
When running the /chrome command in Claude Code, a Chrome tab opens and shows "connecting" status. However, when
pressing Escape to return to the terminal, the connection is not maintained. Subsequent attempts to use browser tools
fail with "Browser extension is not connected" errors.
## Steps to Reproduce
- Run Claude Code in terminal
- Type
/chromecommand - Chrome tab opens showing "connecting" status
- Press Escape to return to terminal
- Try to use any browser automation tool (e.g., tabs_context_mcp)
- Connection fails with "Browser extension is not connected" message
## Expected Behavior
The connection should persist after returning to the terminal, allowing browser automation tools to work.
## Actual Behavior
Connection is lost when pressing Escape. All browser tools report extension not connected.
## Environment
- OS: Windows 11
- Claude Code version: 2.1.29
- Chrome version: 144.0.7559.110
- Extension installed: Yes
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗