openclaw - ๐Ÿ’ก(How to fix) Fix [Bug]: EPIPE on claude-cli live-session spawn (Docker, Unraid, OAuth) [1 comments, 2 participants]

Official PRs (โ€ฆ)
ON THIS PAGE

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
openclaw/openclaw#77178โ€ขFetched 2026-05-05 05:51:24
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
2
Timeline (top)
labeled ร—2commented ร—1renamed ร—1

Running on Unraid via Docker - Container image: ghcr.io/openclaw/openclaw:latest

When using claude-cli via OAuth, OpenClaw fails immediately with EPIPE when invoking claude-cli session.

claude --print "test" works fine in the container as root

Both Sonnet 4.5 and Opus 4.7 fail the same way

Error Message

  1. Receive error when hatching bot [openclaw] Non-fatal uncaught exception (continuing): Error: write EPIPE run error: write EPIPE local ready | error EPIPE error received

Root Cause

Running on Unraid via Docker - Container image: ghcr.io/openclaw/openclaw:latest

When using claude-cli via OAuth, OpenClaw fails immediately with EPIPE when invoking claude-cli session.

claude --print "test" works fine in the container as root

Both Sonnet 4.5 and Opus 4.7 fail the same way

Fix Action

Fix / Workaround

โ ด dillydallyingโ€ฆ โ€ข 1s | local ready
agent main | session main | anthropic/claude-opus-4-7 | tokens ?/1.0m
โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€ [openclaw] Non-fatal uncaught exception (continuing): Error: write EPIPE
at afterWriteDispatched (node:internal/stream_base_commons:159:15)โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€ at writeGeneric (node:internal/stream_base_commons:150:3) at Socket._writeGeneric (node:net:966:11) at Socket._write (node:net:978: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) run error: write EPIPE
local ready | error
agent main | session main | anthropic/claude-opus-4-7 | tokens ?/1.0m
โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€

RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

Running on Unraid via Docker - Container image: ghcr.io/openclaw/openclaw:latest

When using claude-cli via OAuth, OpenClaw fails immediately with EPIPE when invoking claude-cli session.

claude --print "test" works fine in the container as root

Both Sonnet 4.5 and Opus 4.7 fail the same way

Steps to reproduce

  1. Start openclaw onboard
  2. Select Claude CLI and Oauth authentication for model
  3. Receive error when hatching bot

Wake up, my friend!

โ ด dillydallyingโ€ฆ โ€ข 1s | local ready
agent main | session main | anthropic/claude-opus-4-7 | tokens ?/1.0m
โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€ [openclaw] Non-fatal uncaught exception (continuing): Error: write EPIPE
at afterWriteDispatched (node:internal/stream_base_commons:159:15)โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€ at writeGeneric (node:internal/stream_base_commons:150:3) at Socket._writeGeneric (node:net:966:11) at Socket._write (node:net:978: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) run error: write EPIPE
local ready | error
agent main | session main | anthropic/claude-opus-4-7 | tokens ?/1.0m
โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€

Expected behavior

Conversation with bot begins

Actual behavior

EPIPE error received

OpenClaw version

v2026.5.2

Operating system

Unraid

Install method

docker

Model

opus-4.1

Provider / routing chain

openclaw -> cloudfaire-ai-gateway -> minimax

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

The issue is likely due to the claude-cli session invocation failing with an EPIPE error when using OAuth authentication, and a potential workaround is to investigate the authentication flow and ensure proper handling of the claude-cli session.

Guidance

  • Verify that the OAuth authentication is correctly configured and that the tokens are being properly exchanged between OpenClaw and the claude-cli session.
  • Check the claude-cli documentation to ensure that the session invocation is correctly formatted and that any required parameters are being passed.
  • Investigate the differences between running claude --print "test" as root in the container, which works fine, and the claude-cli session invocation, which fails.
  • Consider adding error handling and logging to the claude-cli session invocation to provide more insight into the cause of the EPIPE error.

Notes

The issue may be related to the specific version of OpenClaw (v2026.5.2) or the Docker environment, and further investigation is needed to determine the root cause.

Recommendation

Apply workaround: Investigate the authentication flow and ensure proper handling of the claude-cli session, as the issue is likely related to the interaction between OpenClaw and the claude-cli session.

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โ€ฆ

FAQ

Expected behavior

Conversation with bot begins

Still need to ship something?

ร—6

Another batch ranked right after the header list โ€” different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - ๐Ÿ’ก(How to fix) Fix [Bug]: EPIPE on claude-cli live-session spawn (Docker, Unraid, OAuth) [1 comments, 2 participants]