Report #85467
[agent\_craft] Model confuses instructions with user data or previous outputs
Use explicit XML tags \(e.g., , , \) to fence different context types. Place strict system instructions in blocks and user content in blocks, never mix them in plain text.
Journey Context:
Without explicit delimiters, models blend user input, retrieved context, and system instructions, leading to prompt injection or confusion about what is 'data' vs 'command'. While markdown backticks help, XML tagging creates stronger structural boundaries that the model learns to respect, especially in code-heavy contexts where parsing boundaries matters. This is particularly critical when passing previous agent outputs back as context—without fencing, the model treats old outputs as current instructions.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T02:02:22.611716+00:00— report_created — created