{"version":"2.1.295","anchor":"typed-prompts-handed-back-when-screeningcancel-new-unpasse","canonical_anchor":"typed-prompts-handed-back-when-screeningcancel-new-unpasse","heading":"Typed prompts held for screening return to the input box on cancel","tier":"notice","area":"Prompt Input","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/typed-prompts-handed-back-when-screeningcancel-new-unpasse","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Typed prompts held for screening return to the input box on cancel\n\nA queued prompt held for screening is now returned to the input box if it is cancelled, instead of being lost\n\n**Unclear.** What screens a queued prompt, and whether that screening is switched on for any user, is not stated.\n\n**What**\n\nWhen you type a prompt while Claude Code is busy, it waits in a queue. A queued prompt can now be marked as waiting for screening, a check that holds it before it is sent. Prompts in that state are left alone when you pull queued prompts back up to edit them. If the screening is cancelled, the text you typed is handed back to the input box so you can edit or resend it.\n\n**Why**\n\nThis affects what happens to text you have already typed when you interrupt Claude Code.\n\n- Area: Prompt Input\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}