Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Title: Chrome integration: native host crashes with ERR_INVALID_ARG_TYPE on Windows named pipe creation (Bun runtime) [1 comments, 2 participants]

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…
GitHub stats
anthropics/claude-code#55517•Fetched 2026-05-03 04:51:19
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
chetwerikoffchetwerikoff
Participants
chetwerikoffchetwerikoffgithub-actions[bot]github-actions[bot]
Timeline (top)
labeled ×4commented ×1unlabeled ×1

Error Message

[Claude Chrome Native Host] Socket server error: ...

Error Messages/Logs

[Claude Chrome Native Host] Socket server error: ...

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

Environment:

OS: Windows 11 Claude Code: v2.1.126 (npm install) Runtime: Bun v1.3.14 (Windows x64 baseline) Chrome extension: latest (installed and authenticated)

Repro:

Install Claude Code via npm Install Claude in Chrome extension Run /chrome → "Enabled by default" Run chrome-native-host.bat directly to test

Expected: Native host starts and listens on named pipe. Actual: Crashes immediately with: [Claude Chrome Native Host] Initializing... [Claude Chrome Native Host] Creating socket listener: \.\pipe\claude-mcp-browser-bridge-che [Claude Chrome Native Host] Socket server error: ... TypeError: Failed to listen at \.\pipe\claude-mcp-browser-bridge-che code: "ERR_INVALID_ARG_TYPE" at listen (unknown:1:1) at node:net:1339:30 at listenInCluster (node:net:1423:24) ... Looks like the Bun runtime's Windows named pipe support has an incompatibility with the way net.Server.listen() is called for \.\pipe... paths. This breaks Chrome integration entirely on Windows for this version. The .bat file correctly references the npm-installed binary, registry config and JSON manifest are all valid. Chrome extension is installed, authenticated, and visible. Issue is purely in the native host startup itself.

What Should Happen?

Native host starts and listens on named pipe.

Error Messages/Logs

Steps to Reproduce

Repro:

Install Claude Code via npm Install Claude in Chrome extension Run /chrome → "Enabled by default" Run chrome-native-host.bat directly to test

Expected: Native host starts and listens on named pipe. Actual: Crashes immediately with: [Claude Chrome Native Host] Initializing... [Claude Chrome Native Host] Creating socket listener: \.\pipe\claude-mcp-browser-bridge-che [Claude Chrome Native Host] Socket server error: ... TypeError: Failed to listen at \.\pipe\claude-mcp-browser-bridge-che code: "ERR_INVALID_ARG_TYPE" at listen (unknown:1:1) at node:net:1339:30 at listenInCluster (node:net:1423:24) ...

Claude Model

None

Is this a regression?

No, this never worked

Last Working Version

2.1.126

Claude Code Version

2.1.126

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

VS Code integrated terminal

Additional Information

No response

extent analysis

TL;DR

The issue is likely due to an incompatibility between the Bun runtime's Windows named pipe support and the net.Server.listen() method, causing the native host to crash when trying to listen on a named pipe.

Guidance

  • Verify that the issue is specific to the Bun runtime by trying to run the native host with a different runtime, such as Node.js.
  • Check the documentation for the net.Server.listen() method to see if there are any specific requirements or restrictions for listening on named pipes on Windows.
  • Consider using a different method for creating the socket listener, such as using the net.createServer() method instead of net.Server.listen().
  • Investigate if there are any known issues or workarounds for this problem in the Bun runtime or Node.js documentation.

Notes

The issue seems to be specific to the combination of the Bun runtime and Windows named pipes, and may not be a problem with the Claude Code itself. Further investigation is needed to determine the root cause and find a solution.

Recommendation

Apply workaround: Try using a different runtime, such as Node.js, to see if the issue is specific to the Bun runtime. If the issue persists, consider using a different method for creating the socket listener.

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#inference speed#output truncation#response parsing#generation error

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] Title: Chrome integration: native host crashes with ERR_INVALID_ARG_TYPE on Windows named pipe creation (Bun runtime) [1 comments, 2 participants]