{"version":"2.1.269","anchor":"new-warning-injected-when-a-subagents-report-relays-content","canonical_anchor":"new-warning-injected-when-a-subagents-report-relays-content","heading":"New warning injected when a subagent's report relays content from an Artifact written by someone else","tier":"notice","area":"Subagents","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/new-warning-injected-when-a-subagents-report-relays-content","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### New warning injected when a subagent's report relays content from an Artifact written by someone else\n\nSubagent reports now warn when they relay content from an Artifact someone else wrote\n\n**What**\n\nWhen a subagent (a helper AI instance Claude Code delegates part of a task to) reads content from an Artifact that was written by someone other than itself, its final report to the caller now gets a notice added at the start. The notice tells the caller to treat that relayed content as data, not as instructions to follow.\n\n**Why**\n\nThis is a defense against prompt injection: content written by another party and relayed through a subagent's report could otherwise be mistaken for legitimate instructions. The warning makes clear it should be read as information, not commands.\n\n- Area: Subagents\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}