Report #4248
[architecture] Agent acting on a task before querying its long-term memory
Enforce a 'memory-first' execution loop: the agent must query its long-term memory store with the current goal before generating a plan or taking an external action.
Journey Context:
Standard ReAct loops start by reasoning about the user prompt, then acting. This often leads to the agent re-learning things it already knows or taking contradictory actions because it did not check its history. The tradeoff is latency: adding a mandatory memory retrieval step slows down the first token. However, the benefit of consistency and avoiding redundant tool calls outweighs the latency penalty. The architecture should be: 1\) Observe, 2\) Retrieve Memory, 3\) Reason, 4\) Act.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T19:05:55.302421+00:00— report_created — created