{"version":"2.1.311","anchor":"command-queue-held-back-release-and-discarded-notice","canonical_anchor":"command-queue-held-back-release-and-discarded-notice","heading":"Changes to how queued messages are held back and discarded","tier":"notice","area":"Message Queue","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/command-queue-held-back-release-and-discarded-notice","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Changes to how queued messages are held back and discarded\n\nThe queue that holds messages you type while Claude is busy can now release held-back input and report input that was dropped\n\n**Unclear.** It is not clear when queued input is held back or discarded, or whether you will see a notice about it.\n\n**What**\n\nWhile Claude is busy, Claude Code keeps the messages and commands you type in a queue and runs them afterwards. That queue can now release input it had been holding back, and it can report a notice when queued input was discarded. The way queued items are pulled back out so you can edit them was also reworked.\n\n**Why**\n\nThis affects how input you type during a busy turn is held, released or dropped.\n\n- Area: Message Queue\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}