{"version":"2.1.295","anchor":"prompt-draft-tracks-came-back-state","canonical_anchor":"prompt-draft-tracks-came-back-state","heading":"Restored prompts are tracked in the input box and kept out of history","tier":"internal","area":"Prompt Input","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/prompt-draft-tracks-came-back-state","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Restored prompts are tracked in the input box and kept out of history\n\nThe prompt input now remembers when a draft has come back, keeps it across clears, and restores typed text handed back from the queue\n\n**Unclear.** It is not clear what you see differently when a draft is marked as having come back.\n\n**What**\n\nThe draft in your prompt input box can now be marked as having come back, meaning it was returned to the input rather than freshly typed. Claude Code sets this after checking your prompt hooks. With it:\n\n- the mark survives when the draft is set aside and when it is cleared and restored\n\n- a cleared draft that is being held and carries the mark is not written to your prompt history\n\n- text you typed that is handed back from the waiting queue is now put back into the draft\n\nInserted text is also tidied up before it goes into the draft.\n\n**Why**\n\nThis affects prompts that return to the input after an interruption, so they come back where you can see them without cluttering your history.\n\n- Area: Prompt Input\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}