Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Claude Desktop cannot connect to Claude in Chrome extension in any mode — "No tab available" on Windows, never worked

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

Error: No tab available

Code Example

Error: No tab available
RAW_BUFFERClick to expand / collapse

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 callInputResponse
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 matches what was reported in #38783, though in that case it was a regression after an update. Here it has never worked.

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

  • #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.
  • #38783 — Windows, same degraded 3-tool state. But that issue is a regression after a specific Claude Desktop update. This issue has existed since first install and cannot be a post-update breakage.
  • #48806 — macOS, connection failure in Cowork only. Our issue affects all modes.
  • #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

extent analysis

TL;DR

The issue is likely due to a faulty native messaging host registration on Windows, preventing the Chrome extension from communicating with the Claude Desktop application, and a potential version mismatch between the extension and the desktop application.

Guidance

  1. Verify native messaging host registration: Check if the native messaging host is properly registered on Windows during the installation of Claude Desktop. This might involve checking the Windows registry or configuration files for any errors or inconsistencies.
  2. Check extension and desktop application versions: Although the issue report mentions being on the latest version of Claude Desktop (v2.1.111), the Chrome extension version (v1.0.68) might not be compatible. Verify if there are any known version compatibility issues between the extension and the desktop application.
  3. Investigate platform-specific issues: Given that the issue is specific to Windows and the CLAUDE_CODE_HOST_PLATFORM=win32 environment variable is set, there might be platform-specific code or configuration that is causing the problem. Reviewing the code or configuration related to Windows and native messaging host registration could provide insights.
  4. Review related issues for clues: Although the issue report distinguishes itself from related issues (#21106, #38783, #48806, #50157), reviewing these issues might still provide valuable clues or insights into potential solutions or workarounds.

Example

No specific code example can be provided without more detailed information about the native messaging host registration process or the specific code involved in the communication between the Chrome extension and the Claude Desktop application.

Notes

The issue report suggests that the problem has never worked since the initial install, which implies a potential installation or configuration issue rather than a regression. The fact that the Chrome extension works correctly in the browser sidebar but fails to communicate with the desktop application suggests a specific issue with the native messaging host registration or the communication protocol between the extension and the desktop application.

Recommendation

Apply a workaround by checking the native messaging host registration and ensuring that the Chrome extension and Claude Desktop application versions are compatible. If a compatible version of the extension is available, consider upgrading to that version. However, without more information, it's difficult to provide a specific recommendation for a version upgrade.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#installation#environment variable#network issue#logging issue

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] Claude Desktop cannot connect to Claude in Chrome extension in any mode — "No tab available" on Windows, never worked