{"version":"2.1.309","anchor":"dispatch-and-queued-message-plumbing","canonical_anchor":"dispatch-and-queued-message-plumbing","heading":"Changes to how queued and remote messages are delivered","tier":"soon","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/dispatch-and-queued-message-plumbing","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Changes to how queued and remote messages are delivered\n\nClaude Code changes how it confirms and sends waiting messages, which affects delivery of queued and remote messages\n\n**Unclear.** What this changes for someone using Claude Code is not clear.\n\n**What**\n\nClaude Code changes how it hands over messages that are waiting to be delivered. Delivery confirmations, and the step that sends waiting messages, now wait for earlier confirmations to finish or send waiting answers first. Claude Code also now signals when a request has been committed.\n\n**Why**\n\nThis concerns how reliably queued and remote messages are delivered.\n\n- Flag `tengu_witty_hearth`: Not enough to say (read for one account on one subscription tier against v2.1.309; this account: no value returned, anonymous baseline: no value returned, compiled default: on) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Cloud Sessions\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}