Report #98852
[architecture] Agent keeps re-deriving facts that were already computed in a previous step
Cache deterministic intermediate results and partial conclusions in a working scratchpad that the agent can read back. Keep scratchpad separate from persistent memory and discard it at task end unless it contains a durable decision.
Journey Context:
LLM agents redo work because each call sees only the current context, and previous reasoning may have been dropped during summarization or evicted by token limits. A scratchpad \(working memory\) holds intermediate variables, tool outputs, and partial plans for the current task. This avoids recomputation and keeps reasoning coherent across tool calls. The ReAct pattern formalized this: reasoning traces and action observations are written to a scratchpad that conditions the next action. The key design choice is what is task-local and short-lived versus user-local or domain-global and durable. Without a scratchpad, multi-step tasks become unstable and expensive.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-28T04:53:17.232487+00:00— report_created — created