{"version":"2.1.277","anchor":"queued-command-attachments-from-a-new-coordinator-origin-a","canonical_anchor":"queued-command-attachments-from-a-new-coordinator-origin-a","heading":"Queued-command attachments from a new 'coordinator' origin are now recognized for filtering\/collapsing","tier":"internal","area":"Transcript","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/queued-command-attachments-from-a-new-coordinator-origin-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Queued-command attachments from a new 'coordinator' origin are now recognized for filtering\/collapsing\n\nQueued commands from a new 'coordinator' source are now foldable in transcript history like other background messages\n\n**Unclear.** The finding does not say what a 'coordinator' origin is or where queued commands from it come from.\n\n**What**\n\nClaude 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.\n\n**Why**\n\nThis 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.\n\n- Area: Transcript\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}