{"version":"2.1.323","anchor":"async-repl-output-carries-data-not-instructions-markers","canonical_anchor":"async-repl-output-carries-data-not-instructions-markers","heading":"Claude is told to treat outside text in REPL output as data","tier":"notice","area":"REPL","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/async-repl-output-carries-data-not-instructions-markers","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Claude is told to treat outside text in REPL output as data\n\nREPL output that may contain Artifact content or Remote Control text now carries a note telling Claude to treat it as data, not instructions\n\n**What**\n\nSome command output reaches Claude after a delay. When that output may contain text from people or devices other than you, Claude Code now adds a sentence telling Claude to treat it as data, not instructions. Two cases get the note:\n\n- Artifact content that people other than you may have written.\n\n- Text from a Remote Control session on another device.\n\nThe note stays attached when the output arrives in late pieces.\n\n**Why**\n\nThis guards against prompt injection, where text written by someone else tries to give Claude orders. Claude is told to read such text, not obey it.\n\n- Area: REPL\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}