{"version":"2.1.295","anchor":"prompt-screening-helpers-submitted-text-can-differ-from-typ","canonical_anchor":"prompt-screening-helpers-submitted-text-can-differ-from-typ","heading":"Screened prompts are saved to history as they were actually sent","tier":"notice","area":"Prompt Input","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/prompt-screening-helpers-submitted-text-can-differ-from-typ","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Screened prompts are saved to history as they were actually sent\n\nWhen a prompt is screened, history and the transcript now record the rewritten text, or nothing if the prompt was dropped\n\n**Unclear.** What causes a prompt to be screened, and whether screening runs for a given user, is not known.\n\n**What**\n\nSome prompts are screened (checked before they go to the model). Claude Code now decides what to save from the screening result. This applies both to your input history (the list of earlier prompts you can recall) and to the session transcript.\n\n- A dropped prompt: no history entry is written.\n\n- A rewritten prompt: the rewritten text is stored, not the text you typed.\n\n**Why**\n\nThe text saved in history and in the transcript can now differ from what you typed. Recalling an earlier prompt may bring back the rewritten version, or nothing at all.\n\n- Area: Prompt Input\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}