Mohammed Helaiwa d4b97dc44a fix(agent): drain claude stdout while writing prompt to stdin (#3490) ...

The claude backend wrote the full prompt to the child's stdin and closed
it before starting the stdout reader goroutine. With
--verbose --output-format stream-json the CLI emits a startup banner
before reading its first stdin frame; with no reader draining stdout, the
child blocks on its stdout write, never reads stdin, and our stdin Write
blocks until the per-task context fires. The field symptom is tasks
failing exactly at the 2 h per-task timeout with
"write |1: The pipe has been ended."

Move writeClaudeInput into its own goroutine so the prompt write and the
stdout drain proceed concurrently. Guard stdin close with sync.Once (it
can now be called from both the writer goroutine and, previously, the
result handler). Join the write result at cmd.Wait() and surface a write
failure as a "failed" status only when no result event arrived and no
session was established, so a genuine startup death still reports the
stderr tail.

Add a regression test that re-execs the test binary as a fake claude
which bursts 256 KiB to stdout before reading stdin, with a 128 KiB
prompt pushed at stdin — both past any plausible OS pipe buffer — so a
regression hangs until the test deadline instead of passing.

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

2026-06-01 13:52:41 +08:00

..

agent

fix(agent): drain claude stdout while writing prompt to stdin (#3490)

2026-06-01 13:52:41 +08:00

db

fix(comments): preserve direct parent on replies (#3579)

2026-06-01 08:28:15 +08:00

protocol

feat: support local working directory for projects (MUL-2618 v1) (#3283)

2026-05-27 13:44:31 +08:00

redact

feat(security): redact sensitive information in agent live output

2026-03-30 23:38:49 +08:00