Codeman maintainer 0aa16cd4d3 docs(skill): never branch on .status, it is wrong in both directions ...

Measured on a live claude worker: `GET /api/v1/sessions/:id` reported
`status: "idle"` while the worker was mid-turn and actively producing output, with
`lastActivityAt` equal to the moment of the call. The skill already warned that a
worker which dies inside its pane also reads `idle`, so the field is unreliable in
both directions and nothing an agent does should depend on it.

Synchronize on `stop` via send-and-wait or on an output marker. To judge from
outside, sample `terminal?tail=` twice a few seconds apart: a changing buffer is the
only cheap positive proof a worker is still working. `wait?until=exit` stays the
death check.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-08-09 12:29:15 +02:00

..

reference

docs(skill): never branch on .status, it is wrong in both directions

2026-08-09 12:29:15 +02:00

SKILL.md

docs(skill): never branch on .status, it is wrong in both directions

2026-08-09 12:29:15 +02:00