[BUG] Claude Desktop cannot connect to Claude in Chrome extension in any mode with "No tab available" on Windows

[MajorMajorMajorMajor]

Preflight Checklist

• I searched existing issues before filing this
• This is one bug per report
• I am on the latest version (v2.1.111)

---

What's Wrong?

The Claude in Chrome extension has never successfully connected to the Claude Desktop application on Windows, in any mode (chat, Claude Code, or Cowork). Every tab operation returns No tab available immediately, with no additional detail.

The Chrome extension itself is fully functional — Claude operates correctly from the browser sidebar, can navigate pages, interact with elements, and fill forms. The broken link is specifically between the extension and Claude Desktop.

---

What Should Happen?

Claude Desktop should be able to list, access, and interact with open Chrome tabs via the extension, across all modes.

---

Error Messages / Logs

All tab operations return the same error with no further detail:

Error: No tab available

Exact calls attempted and responses:

Tool call	Input	Response
browser_batch → tabs_list	{}	Error: No tab available
browser_batch → tabs_context_mcp	{"createIfEmpty": false}	Error: No tab available
browser_batch → tabs_context_mcp	{"createIfEmpty": true}	Error: No tab available
browser_batch → screenshot	{}	Error: No tab available

Note: createIfEmpty: true should create a new tab group from scratch — its failure suggests the MCP server has no connection to the extension whatsoever, not merely a missing tab group.

Tools present (3): browser_batch, tabs_close_mcp, file_upload
Tools absent: navigate, read_page, click, find, javascript_tool, tabs_context_mcp, screenshot, and all other interaction tools

This degraded 3-tool state superficially resembles what was reported in #38783, although that issue affects computer use, an entirely different component.

---

Steps to Reproduce

1. Install Claude Desktop on Windows and sign in
2. Install the Claude in Chrome extension (v1.0.68) in Chrome
3. Verify the extension works — open the sidebar in Chrome, confirm Claude can interact with page content
4. Open Claude Desktop in any mode (chat, Claude Code, or Cowork)
5. Open Chrome with at least one active tab
6. Attempt any tab operation (navigate, screenshot, tabs_context_mcp, etc.)
7. Observe: Error: No tab available regardless of mode or call

---

System Information

• Claude Desktop version: 2.1.111 (claude --version)
• Claude in Chrome extension version: 1.0.68
• Chrome version: 147.0.7727.102 (Official Build) (64-bit)
• OS: Windows
• API platform: Anthropic (direct)
• Regression: No — has never worked on this machine since initial install

---

Why This Is Different From Related Issues

• Chrome integration: tabs_context_mcp works but all tab operations fail with 'No tab available' #21106 — Same No tab available symptom, but macOS only. Described as a regression where tabs_context_mcp lists tabs successfully before other calls fail. In our case, tabs_context_mcp itself fails immediately. Platform and failure mode differ.
• [BUG] Windows: Cowork browser automation tools missing after Claude Desktop update — computer-use tools never register #38783 — Windows, similar degraded 3-tool state. But that issue pertains to the computer use MCP rather than to the Chrome extension
• [BUG] Claude in Chrome + Control Chrome Failures in Cowork Mode #48806 — Chrome extension also broken, but on a different platform (macos) and with a different symptom and error message about failing to connect to the extension. In our case, Claude reports success in establishing the connection, but then fails with a different error when attempting to interact with it
• [BUG] Claude in Chrome extension (v1.0.68) blocks navigation to claude.ai — breaking MCP browser automation after recent update #50157 — Extension v1.0.68 blocking navigation to claude.ai (macOS). Unrelated symptom and platform.

---

Additional Context

• The extension↔Desktop bridge appears entirely non-functional on Windows from first install, suggesting a possible issue with native messaging host registration on Windows during installation
• Environment confirms CLAUDE_CODE_HOST_PLATFORM=win32

[github-actions]

Found 3 possible duplicate issues:

1. [BUG] Windows: Cowork browser automation tools missing after Claude Desktop update — computer-use tools never register #38783
2. [Bug] Claude in Chrome MCP bridge fails on Windows - socket discovery doesn't find named pipes #21337
3. Claude-in-Chrome MCP fails to connect on Windows 11 — named pipe not created #45558

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

[MajorMajorMajorMajor]

Not a duplicate.

[Squall98]

I have the same problem.

[daviddaleypowerhealthondemandcom]

I had this problem and it turned out to be that I had the chrome extension installed in another user profile. I remove the plug in from that profile, then ran tabs_context_mcp({ "createIfEmpty": true }) in the code console and it created the group and can now connect ok.