Under the hood
Queued commands from a new 'coordinator' source are now foldable in transcript history like other background messages
What
Claude Code already collapses certain transcript entries during history filtering and compaction, such as channel messages, peer messages, Slack pings, and task notifications. A new check now also recognizes 'queued_command' attachments whose origin is a 'coordinator', treating them the same way: as candidates for folding or skipping when trimming transcript history.
Why
This keeps transcripts from a coordinator source consistent with other background-origin messages, so they don't clutter the visible history any more than channel or task notifications already don't.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
The finding does not say what a 'coordinator' origin is or where queued commands from it come from.