Report #96449
[agent\_craft] Agent retrieves too much context upfront 'just in case', diluting the prompt and confusing the task
Adopt an iterative retrieval pattern. Start with a minimal context \(the task itself\), let the agent plan, and retrieve specific information only as needed via targeted tool calls.
Journey Context:
The 'kitchen sink' approach to context—loading every potentially relevant file, API doc, and database schema before the agent starts—guarantees context rot and high latency. The agent gets overwhelmed by information it doesn't need yet. Iterative retrieval \(ReAct pattern\) treats context gathering as an action. The agent reads the task, realizes it needs a specific API schema, retrieves it, acts, and retrieves the next piece. This keeps the context lean and highly relevant to the immediate step, drastically improving reasoning accuracy.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T20:28:33.803526+00:00— report_created — created