{"version":"2.1.319","anchor":"queued-commands-connector-origin-and-task-delivery-changes","canonical_anchor":"queued-commands-connector-origin-and-task-delivery-changes","heading":"Queued messages now reach the model with their text unchanged","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/queued-commands-connector-origin-and-task-delivery-changes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Queued messages now reach the model with their text unchanged\n\nQueued commands and teammate messages are now passed to the model as written, and queued items can be marked as coming from a connector\n\n**What**\n\nA queued command is a message you type while Claude Code is still busy, held until the current work finishes. Claude Code used to run the text of queued commands, and of messages from teammates, through an extra rewriting step before sending them on. That step has been removed, so the text now reaches the model exactly as written.\n\nQueued items can now also be marked as coming from a connector, which is a link to an outside service. Some delivery details for background tasks are dropped in certain conditions.\n\n**Why**\n\nThis changes how queued messages arrive at the model, so what Claude sees for a queued message may differ slightly from before.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}