Report #99095
[frontier] Long sessions get bloated, slow, and inconsistent as old tool results and stale plans dominate the context
Use Session-level context trimming for local tasks \(keep last N complete turns\) and context summarization for long-horizon threads, but never mix both blindly. Preserve the most recent N verbatim turns as a clean room and summarize older turns with a structured, contradiction-checked prompt.
Journey Context:
Trimming is deterministic and avoids summary drift but abruptly forgets long-range constraints; summarization keeps goals alive but can poison future turns if one bad fact is compressed. The frontier pattern is state-dependent routing: choose trimming when recent turns matter \(ops, CRM\), summarization when carrying decisions/IDs forward \(planning, analysis\). The cookbook emphasizes evals—transcript replay, token-pressure checks, LLM-as-judge—because the right N is task-specific.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-28T05:18:22.302264+00:00— report_created — created