{"version":"2.1.277","anchor":"pasted-content-is-now-screened-and-can-be-stripped-from-the","canonical_anchor":"invisiblehidden-characters-stripped-from-pasted-or-typed-pr","heading":"Invisible and hidden characters are now stripped from prompts before sending","tier":"notice","area":"Fleet","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/pasted-content-is-now-screened-and-can-be-stripped-from-the","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Invisible and hidden characters are now stripped from prompts before sending\n\nPasted or typed text with invisible\/hidden characters is now cleaned and flagged before it's sent, including in fleet composers\n\n**What**\n\n- Before a prompt is submitted, or before pasted text is sent, Claude Code now runs it through a filter that removes invisible characters, such as bidi marks, zero-width characters, hidden tags, and similar hidden selectors.\n\n- If any such characters are found, sending is blocked. Instead you see a notice like \"Removed N invisible character(s) \u00b7 review and press Enter to send\" (or a message that nothing is left to send), and the text is replaced with the cleaned version so you can review it before sending again.\n\n- The same protection now applies to the fleet command bar and the fleet reply composer, not just the main prompt input.\n\n**Why**\n\nInvisible or hidden characters can be used to hide instructions inside pasted text or make it look different from what it actually contains. Stripping them and asking for confirmation before sending prevents accidentally sending something you didn't intend to.\n\n- Area: Fleet\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}