{"version":"2.1.280","anchor":"queued-message-submission-now-uses-the-drafts-live-permissi","canonical_anchor":"queued-message-submission-now-uses-the-drafts-live-permissi","heading":"Queued message submission now uses the draft's live permission mode","tier":"notice","area":"Message Queue","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/queued-message-submission-now-uses-the-drafts-live-permissi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Queued message submission now uses the draft's live permission mode\n\nSending a queued message now uses whatever permission mode is currently active, not the one from when it was queued\n\n**What**\n\nWhen a message is queued up and then submitted, either through `submitEmpty` or by using `sendQueuedNow` to send it immediately, Claude Code now builds the submission using the draft's current permission mode (or an explicitly passed mode), instead of a mode that was fixed at an earlier point.\n\n**Why**\n\nIf the permission mode is changed while a message sits in the queue, the queued send now reflects that updated mode rather than sending under the stale mode it was queued with.\n\n- Area: Message Queue\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}