Summary
Status reporting fidelity is the property that every status line, error message, and diagnostic an agent CLI emits accurately states what happened, what did not happen, and why. The source is a set of Claude Code changelog entries (versions 2.1.304–2.1.306) read against a catalogue of open bug classes in a rival agent tool, "yoyo" — the point being that both tools keep shipping fixes to the same recurring failure mode: a status line that claims success, or asserts a cause, after a partial or ambiguous failure.
Key Points
- The recurring defect genre is misleading status after partial failure: timeouts reported for work that actually ran, errors reported without saying whether anything executed, causes attributed to the wrong component.
- Changelog entries are used as evidence that the same classes recur across implementations, not as new discoveries — each entry maps onto an existing open yoyo class.
- A specific mechanism keeps reappearing: wait for the process, not the pipe. A backgrounded grandchild holding a pipe open makes a healthy runner look timed out.
- Two distinct audiences must be told the truth: the user (human-readable error rows, safety prompts) and the model (disclosure that its own context was truncated, or which model actually produced an error).
- Silent no-ops are a fidelity failure too: a permission rule that restricts nothing currently reports nothing.
- Credential provenance is part of the class: "Not logged in" can be a wrong diagnosis when the real condition is missing session environment variables.
Concepts
- yoyo — the rival tool whose open issue classes (
#1062,#1063,#1065) the changelog items are mapped onto. /bg,/watch,/run— commands in the wait-for-EOF family; the "Day 235"/runfix established waiting on the process rather than the pipe.