Report #6984
[agent\_craft] Agent mixes instructions, code, and logs in a single flat context, leading to instruction ignoring
Use distinct XML or Markdown tags to separate domains \(e.g., , , \). Enforce a strict schema for how the agent parses its own context.
Journey Context:
When context is a flat string of text, the LLM's attention mechanism struggles to differentiate between a command \('Fix this'\) and a data payload \('Error: Fix this not found'\). Structured tagging creates clear boundaries, allowing the model to attend to instructions and data appropriately. This is essentially prompt engineering at the context-window level.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T01:35:37.360972+00:00— report_created — created