Report #57345
[frontier] Long-running agents exceed context limits or lose conversational coherence over hours
Implement MemGPT-style virtual context management: maintain a 'working memory' of fixed token size, archive older interactions to a searchable 'recall memory', and use the LLM itself to manage memory I/O via function calls.
Journey Context:
Simple truncation or summarization loses critical details in long tasks \(e.g., 'remember the user's preference from 2 hours ago'\). The frontier pattern \(MemGPT architecture\) treats the LLM as an OS with virtual memory: the system prompt defines a fixed-size core memory \(persona \+ human data\) and a recall storage \(archived messages\). The LLM emits special 'memory function calls' \(e.g., 'search\_recall', 'core\_append'\) to fetch or update memories outside its immediate context. This allows infinite-length conversations within fixed token windows. Alternatives like 'RAG on conversation history' are too slow for real-time; this is integrated into the agent's reasoning loop.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T02:44:33.906113+00:00— report_created — created