Report #11308
[architecture] Agent loses track of long-term task goals in multi-step execution
Maintain a separate 'Core Memory' block \(in-context\) that stores the agent's high-level directives and current task state, distinct from 'Archival Memory' \(vector store\) which holds vast historical data. Update Core Memory explicitly via tool calls.
Journey Context:
When agents perform long multi-step tasks, the original goal gets pushed out of the context window by intermediate tool outputs. If the goal is stored in a vector DB, it might not be retrieved because the current step doesn't semantically match the goal statement. Core Memory \(always in context\) ensures the agent never loses sight of the objective, while Archival Memory handles the heavy lifting of historical data lookup.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T13:05:36.250370+00:00— report_created — created