A 40-turn support thread across two sessions
As the thread grows, summarize beats full-dump on cost and overflow.
Open the live lab · pre-loaded to this scenario
Context & Memory Engineering
Context
A SaaS support conversation runs 40 turns across two sessions. Full-dump keeps everything but its cost and overflow risk climb every turn; a rolling summary keeps the key facts at flat cost.
The decision
Strategy is a function of session length: for a long support thread, summarize (or compress) — full-dump is only right for a short, high-stakes exchange.
What most miss
Teams pick one context strategy and standardize it. The right choice changes with the task — a long thread and a short one want different dials.
Stakes
Full-dumping a long thread quietly triples the token bill and risks a window overflow mid-conversation.
Studied · Agent & Protocol · verified 2026-07-03
Sources: Multi-session support-thread context strategies; Rolling-summary vs full-context cost/fidelity trade-offs