Context Budget for Long Conversations — the History Eats the Window
Every turn resends the whole history. Budget a growing chat: how much window the conversation already consumes and how many turns of life it has left.
Overview
Conversations fail by accumulation: each turn carries the entire history, so the budget consumed grows even when the new message is one line. This scenario loads a long chat history against a maximum response reservation — the realistic late-conversation state — and lands at Likely Safe with the consumption made explicit. The planning insight is the trajectory: a history at 60% today gains the same again in half as many further turns. The guidance covers the conversation-specific moves — and when the history finally will not fit, carrying a compact state package into a new chat (the Context Handoff Builder's job) beats pasting the transcript.
Workflow
-
Paste the real history
The accumulated transcript is the input — that is what every next turn actually resends.
-
Read consumption as trajectory
60% used is not "fine" — it is a countdown measured in turns, not tokens.
-
Plan the handoff point
Choose the exit before the window forces it — compact state beats pasted transcript.
Why This Works
- Accumulation framing explains failures that single-message checks miss
- Trajectory thinking converts a percentage into remaining turns
- A planned handoff preserves what a forced one loses
Best for
- Long iterative working sessions
- Conversations that degraded after dozens of turns
- Planning handoff points before forced ones
Not for
- Building the handoff package itself — that's the Context Handoff Builder
- Distilling the conversation into a reusable prompt — that's the Conversation-to-Prompt Builder
Use cases
- Checking how much life a long session has left
- Explaining late-conversation quality drops
- Deciding when to hand off to a fresh chat