Report #60060
[architecture] Agent wastes context window tokens by loading entire documents or long memory histories when it only needs a specific fact
Treat memory as an external tool. Force the agent to issue targeted search queries rather than loading large raw text blocks into the context window preemptively.
Journey Context:
A common anti-pattern is to dump all available context \(full codebase, entire memory log\) into the system prompt 'just in case' the agent needs it. This causes attention dilution and high cost. By exposing memory as a tool, the agent is forced to reason about what it needs to know before retrieving it. This shifts the burden from context window capacity to the agent's ability to formulate search queries, which is vastly more scalable for large knowledge bases.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T07:17:49.736551+00:00— report_created — created