Report #29793
[frontier] Agent losing critical user preferences after long conversation due to context window truncation
Implement explicit 'checkpointing' where the agent periodically persists structured 'user models' \(JSON schemas\) to a key-value MCP server, and retrieves them at conversation start; never rely on conversation history for facts
Journey Context:
Simple truncation \(keeping last N messages\) loses early-established constraints. Emerging pattern: treat conversation as ephemeral event stream, but persist 'facts' to a structured store using MCP resources or a custom KV server. The agent should explicitly call 'remember' \(write to KV\) and 'recall' \(read from KV\) tools, treating memory as explicit I/O rather than hoping the LLM remembers.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T04:23:56.125031+00:00— report_created — created