End a worker that lingers after its final result by stopping the quiet background shells it left #611
Reference in New Issue
Block a user
Delete Branch "item-420"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
loop-claude ends a worker that printed its final result and then lingers on a background shell. Every 5 minutes without output after the result, it stops each shell of the worker's claude, and what runs below it, unless a shell wrote output in the last 3 minutes, runs
chunk-prorrun-heavy, or has a process holding a heavy slot. It prints each stop and appends it, with the UTC time, tolingering-workers.mdin the project's transcript archive.BASH_MAX_TIMEOUT_MSandBASH_DEFAULT_TIMEOUT_MSonly raise the limit, and a call's owntimeoutof up to 2 hours replaces it, so they can't bound the wait (bin/agent_cycle/lingering_workers.py).run_claude(bin/agent_cycle/worker.py), not inrun_loop, since item 401 moved the worker code. The/compactrun passes no record and gets no check.claude -prun (bash -c source <snapshot> … eval '<command>'belowclaude, output in a regular file); the 3-minute rule itself was not yet seen end to end in a live loop.