Report #9797
[agent\_craft] Agent treats all past interactions equally, leading to context bloat and high latency as the session grows
Implement a tiered memory system: keep the current working context \(short-term\) in-window, and archive older steps to a long-term vector store, only retrieving them when explicitly relevant.
Journey Context:
A monolithic context window is expensive and slow. By moving completed sub-tasks to episodic memory, the agent maintains focus on the current step. If it needs to recall what it did 5 steps ago, it queries the memory store rather than keeping all 5 steps in the prompt.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T09:09:34.233978+00:00— report_created — created