Report #67715
[agent\_craft] Agent uses a single monolithic context block for all tasks causing conflicting instructions
Implement a context router that swaps system-level instructions and few-shot examples based on the current sub-task, rather than keeping all instructions in the context simultaneously.
Journey Context:
Loading 'how to write code' and 'how to write tests' instructions together causes interference and wastes context. A router identifies the intent \(e.g., 'edit file' vs 'run test'\), and injects only the relevant persona/instructions. This keeps the context lean and focused, reducing hallucination from conflicting directives.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T20:08:21.534519+00:00— report_created — created