Report #97253
[agent\_craft] Agent calls tools for information it already has in context
Maintain an explicit working-memory digest of facts the model has already obtained. Before issuing a search/read tool, check whether the answer is already in that digest and route the model to use it.
Journey Context:
A common failure mode is reading the same file twice, re-listing a directory, or re-querying an API because earlier results scrolled out of the immediate context window or because the model did not connect a prior result to the current question. The cheap fix is a short "facts learned" block that is updated after each tool call and kept near the top of the context. More robust systems use a tiny retrieval/index layer. This is essentially the ReAct observation step turned into durable memory: the model's observations are materialized so they do not need to be re-derived. The alternative is endless redundant tool calls, which burn tokens and slow execution.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-25T04:48:39.430641+00:00— report_created — created