Report #101606
[architecture] Agent forgets long-running task constraints after a few turns
Keep a small, protected scratchpad or goal stack in working memory and re-inject it into every prompt. Do not rely on retrieval alone for active task state.
Journey Context:
LLMs lose track of constraints not because retrieval fails but because active context is crowded by intermediate reasoning. Retrieval is too slow and noisy for in-flight task state; you need a pinned scratchpad that survives each turn. The common mistake is putting goals in the vector store and hoping similarity pulls them back. The tradeoff is a few hundred fixed tokens, but that cost is lower than recovering from a derailed task.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-07T05:08:28.611079+00:00— report_created — created