EADDRINUSE: address already in use
A port Claude Code wanted to bind is already held by another process.
30 issues · 5 open · 25 resolved (83%) · first seen Aug 22, 2025
First response · network
What to do now
Most likely: A DNS, proxy, TLS or socket layer interrupted the connection.
- Check whether the same request works without the current VPN or corporate proxy.
- Verify DNS and certificate trust without disabling TLS verification.
- Capture the hostname and exact socket code before escalating.
These are conservative triage steps, not an official Anthropic fix. Use the issue and workaround evidence below before making a destructive configuration change.
Is this getting better or worse?
This class of problem is holding steady. 7 new reports in the last 90 days vs 6 in the 90 before — +17%. The open backlog peaked at 6 in 2026-02 and sits at 5 today.
Derived by counting each matching issue from its creation date until it closed. First-party
computation over the anthropics/claude-code tracker — the trend is not published
anywhere upstream.
Which builds report this
20 of these reports name the Claude Code build they were running, spanning 16 releases. Heaviest reporters:
- Claude Code v2.1.29
- Claude Code v2.1.37
- Claude Code v2.1.30
- Claude Code v2.1.251
- Claude Code v2.1.229
- Claude Code v2.1.224
- Claude Code v2.1.220
- Claude Code v2.1.197
Report volume, not a defect count: an issue can mention a build without that build having caused the failure. Versions come from the version string in the bug-report template, matched against real published tags.
Do these get fixed?
Median time to close is 12 days across 25 closures. Of the 25 closures with a recorded reason, 20% were closed as completed and 20 as not-planned or duplicate. The most recent completed fix landed in 2026-08.
Workarounds reported by the community
13 of these issues post a workaround someone says worked. The highest-engagement ones:
- Chrome Extension: EADDRINUSE - Native Host and MCP Server both try to create pipe listener
- …s Involved Native Messaging Host Config: Native Host Batch: Workaround None found yet. --- Reported via Claude Code
Found in the description of #21791 · resolved - [BUG] Windows: Chrome extension native host crashes with EADDRINUSE pipe conflict
- …r), run: 7. Native host crashes immediately with EADDRINUSE Workaround: Use Claude Code version 2.1.19, which works correctly. Claude Model None Is this a regression? Yes, this worked in a previous version Last Working V…
Found in the description of #21512 · resolved - Bug: Claude Preview MCP panel opens in wrong session (multi-session Desktop)
- …Primary working directory: - with 7-13 named server entries Workaround I'm Currently Using My Claude sessions now avoid entirely and instead start dev servers via Bash, then use with to point at . This is clunky but avoi…
Found in the description of #62290 · resolved - [BUG] Chrome MCP fails with EADDRINUSE: native host tries to create new pipe server instead of connecting to existing one
- …g., ) 5. Observe "Browser extension is not connected" error Workarounds Attempted (None Worked) - Restarting Chrome - Restarting Claude Code - Killing old node processes - Reloading the Chrome extension - Clicking the ex…
Found in the description of #22651 · resolved - [BUG] Daemon supervisor (transient) hard-exits on EADDRINUSE during control-socket bind race — regression in 2.1.195
- …, so it's not mode-specific. Note: the roster.json-clearing workaround discussed over in 68146 does not fix this, and in our case triggered a separate, more destructive bug — see my comment there for details.
Found in the thread of #72334 · still open
Excerpts are quoted from the linked issue so you can judge relevance before opening it. Threads that only ask for a workaround, or report that there is none, are excluded. These are community suggestions, not official guidance from Anthropic — read the full thread before applying one.
Matching issues 1–30
Ranked by community engagement (reactions weighted over comments).
- Chrome Extension: EADDRINUSE - Native Host and MCP Server both try to create pipe listener
- [BUG] Windows: Chrome extension native host crashes with EADDRINUSE pipe conflict
- Chrome extension not connecting to Claude Code via native messaging on Windows 11
- Bug: Claude Preview MCP panel opens in wrong session (multi-session Desktop)
- [BUG] Chrome MCP fails with EADDRINUSE: native host tries to create new pipe server instead of connecting to existing one
- Memory system not automatically consulted after context compaction
- Claude in Chrome: Múltiplas instâncias do native host causam erro EADDRINUSE no Windows
- Title: Claude Chrome Extension Unable to Connect to Claude Code CLI Despite Correct Configuration
- Unhandled Process Termination in Claude Code CLI
- [BUG] Daemon supervisor (transient) hard-exits on EADDRINUSE during control-socket bind race — regression in 2.1.195
- [BUG] Claude Desktop v1.1.7053 spawns two mcp-remote processes simultaneously during MCP server initialization, causing OAuth PKCE auth to fail
- [BUG] Port conflict when multiple mcp-remote instances start simultaneously
- `claude-in-chrome` extension fails to connect on Windows when Claude Desktop is also installed — workarounds insufficient
- [BUG] Chrome native host crashes with EADDRINUSE on Windows - named pipe conflict
- [BUG] Claude Code caused server outage by unauthorized SSH login and destructive PM2 commands
- [BUG] Chrome extension connection fails on Windows - named pipe EADDRINUSE conflict
- Windows: Chrome extension connection broken in 2.1.37, works in 2.1.19 (EADDRINUSE pipe conflict)
- [Windows] EADDRINUSE: multiple --claude-in-chrome-mcp processes compete for the same named pipe
- [Windows] Chrome extension reconnect fails - page closes immediately
- Pipe conflict: Claude Code and native host fighting over claude-mcp-browser-bridge-apirr (EADDRINUSE)
- Chrome integration: EADDRINUSE on Windows - MCP server and native host compete for named pipe
- Claude Code Repeatedly Requests Self-Termination Permissions Without Clear User Communication
- chrome-native-host crashes on every invocation (Windows, ERR_INVALID_ARG_TYPE on named pipe listen)
- [Windows] Stale daemon.lock + PID reuse after unclean shutdown deadlocks the transient daemon (every spawn logs "another daemon won the lock race" and exits)
- [BUG] Chrome native host and Claude Code compete for same named pipe (EADDRINUSE on Windows)
- Claude in Chrome: native host broadcasts every tool response to all connected MCP clients — concurrent sessions silently receive each other's results
- [BUG] 2.1.154 regression: deep CLAUDE_CODE_TMPDIR overflows macOS UNIX-socket sun_path, breaking bundled playwright-cli daemon (EADDRINUSE)
- [DOCS] Edge support contradicts between Claude Code Chrome docs and Help Center article (Edge works with Claude Code)
- [BUG] OAuth callback listener uses a hardcoded port A53280 with no fallback
- [FEATURE] A port-allocation coordination primitive for concurrent sessions (re-file of #34385)