›_ Claude Code Issues
Claude Code Issues / Error strings / EPIPE: broken pipe

EPIPE: broken pipe

Claude Code wrote to a pipe whose reader had already gone away.

60 issues · 4 open · 56 resolved (93%) · first seen Feb 24, 2025

First response · local

What to do now

Most likely: The operating system rejected a file or directory operation.

  1. Read the first path in the error and verify that it exists and belongs to the expected user.
  2. Check disk space, permissions, symlinks and whether another process holds the target.
  3. Reproduce with the smallest affected path before changing project-wide permissions.

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 converging. 4 new reports in the last 90 days vs 6 in the 90 before — -33%. The open backlog peaked at 4 in 2025-07 and sits at 4 today.

0 1 2 3 4 2025-022025-092026-042026-10
2025-02 — First reports2025-07 — Peak backlog (4 open)

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

13 of these reports name the Claude Code build they were running, spanning 12 releases. Heaviest reporters:

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 4 days across 56 closures. Of the 56 closures with a recorded reason, 36% were closed as completed and 36 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:

Node.js EPIPE Error on Bash Command Execution
…ng to 1.0.54 seems fine. For other suffering the pain (temp workaround):
Found in the thread of #3881 · resolved
Unhandled EPIPE Error Causing Node.js Application Crash
…bove - crashes during operation with work in progress lost. Temporary fix applied: Following the suggestion in this thread, I've disabled PostToolUse hooks in and will test if this resolves the issue. Status: Testing the…
Found in the thread of #2834 · resolved
[BUG] Connection-level errors (ECONNRESET, EPIPE, ETIMEDOUT) are never retried — immediate failure with zero recovery
…+ partial retry reimplementation is the core issue. Partial workaround: PostToolUseFailure hook to auto-retry You can't retry API calls from a hook, but you can detect connection-related failures and alert: Better workar…
Found in the thread of #37077 · resolved
[BUG] Cowork on macOS 1.8555.2 — zero MCP tools bind in any install path (.mcpb + SDK bridge + Custom Connectors + project .mcp.json); spawn pipeline missing --mcp-config since 2026-05-23 auto-update
Update — workaround validated empirically, regression boundary confirmed Following up after running the same-machine, same-config A/B comparison to nail down whether 1.8555.2 is genuinely the regression point. Method - O…
Found in the thread of #62072 · still open
Error: write EPIPE
Found the a workaround: Seems caused because I'm using FISH, which the isn't supported?
Found in the thread of #47 · resolved

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–60

Ranked by community engagement (reactions weighted over comments).

Related aggregations

  1. ENOENT: no such file or directory

    1,241 issues

  2. EISDIR: illegal operation on a directory

    497 issues

  3. EACCES / EPERM: permission denied

    453 issues

  4. ENOTEMPTY: directory not empty

    90 issues

  5. EEXIST: file already exists

    142 issues

  6. EBUSY: resource busy or locked

    141 issues