2 people reported
All time, since Sep 14.
Headless run kills running background subagents yet exits success
“So subagents that are actively working (writing files, running tests) are killed exactly 600 s after the main thread went quiet.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/claude-code/issues/802/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
claude -p stops in-flight subagents after the main thread goes idle, then reports result.subtype: "success" and exit code 0.
Is this your bug?
File my report- Where
- headless print mode
- Versions
- 2.1.270 to 2.1.284
- Platforms
- Linux
- How bad
- Breaks a normal workflow.
Not quite your bug?
- Finished Bash calls stuck Running2 people
- Orphaned processes after task stop8 people
- Ceiling kill loses cause6 people
Original reports2, newest first
claude -pkills actively-working background subagents 600 s after the main thread goes idle, calls it "user rejected", and exits 0 with result: success#98170- Headless
claude -pexits with its own background subagents still running; every in-flight Task is reportedstoppedand the run still endsresult.subtype=success, exit code 0#94392