Error: write EPIPE
Status Fixed / completed
Maintainer reply ✓ Yes — igorkofman
Workaround ✓ Mentioned in thread ↓
Activity 7 comments · opened Feb 25, 2025 · closed Mar 6, 2025
💡 Likely answer: A maintainer (igorkofman, collaborator)
responded on this thread — see the highlighted reply below.
CLI app crashed after authenticated.
And try to run claude again, it crashed with an EPIPE error.
Error: write EPIPE
at afterWriteDispatched (node:internal/stream_base_commons:161:15)
at writeGeneric (node:internal/stream_base_commons:152:3)
at Socket._writeGeneric (node:net:954:11)
at Socket._write (node:net:966:8)
at writeOrBuffer (node:internal/streams/writable:570:12)
at _write (node:internal/streams/writable:499:10)
at Writable.write (node:internal/streams/writable:508:10)
at m8.sendToShell (file:///Users/____/.local/share/nvm/v20.17.0/lib/node_modules/@anthropic-ai/claude-code/cli.mjs:339:243)
at file:///Users/____/.local/share/nvm/v20.17.0/lib/node_modules/@anthropic-ai/claude-code/cli.mjs:337:1614
at new Promise (<anonymous>) {
errno: -32,
code: 'EPIPE',
syscall: 'write'
}
MacOS v15.3
Warp Shell v0.2025.02.19.08.02.stable_05
Claude code v0.2.9
Node lte/iron (v20.17.0)
7 Comments
claude doctorreturns all green.!Image
calude -d --verboseandclaude /clearall crashed on start!Image
Every command starts with
/crashes, including/bug/costor even/logoutor/doctorbut without/one works, such asdoctororconfig.I also get "write EPIPE" errors when using bash mode
<img width="536" alt="Image" src="https://github.com/user-attachments/assets/90bee66c-1511-43d5-ab9e-b8516a9d28c4" />
Found the a workaround:
SHELL=/bin/bash claudeSeems caused because I'm using FISH, which the
claude-codeisn't supported?Will try. I'm using fish as my default shell but I'm actually calling claude-code from bash. claude-code probably shouldn't default to the defaultshell if it doesn't support them....
This should be fixed in the latest version - let us know if you're still seeing this issue.
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.