{"version":"2.1.286","anchor":"queued-message-head-readiness-is-now-scoped-by-agentid","canonical_anchor":"queued-message-head-readiness-is-now-scoped-by-agentid","heading":"Queued messages are no longer held up by another agent's messages","tier":"notice","area":"Message Queue","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/queued-message-head-readiness-is-now-scoped-by-agentid","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Queued messages are no longer held up by another agent's messages\n\nWhether a queued message can be delivered now depends only on that agent's own messages, not on other agents' waiting ones\n\n**Unclear.** What the earlier check matched is not known, so it is unclear how often messages were actually held up before.\n\n**What**\n\nWhen you or Claude send messages while work is in progress, they wait in a queue. Claude Code checks the front of that queue to see whether a message can be delivered. That check now only looks at messages belonging to the same agent (a separate Claude instance handling part of a task). Messages from a different agent that are waiting, or marked to go now, no longer stop this agent's message from being delivered.\n\n**Why**\n\nThis can stop one agent's queue from getting stuck behind messages meant for another agent.\n\n- Area: Message Queue\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}