Every request you send Claude has a context window. A million tokens sounds like a lot, but it runs out faster than you think once you're shipping a real agent. That's where context management comes in: it's how you stay inside the window without losing what matters.
Context is everything Claude sees on a given turn:
It's the input to every single API call. You pay for it on the way in, and you pay for it on the way out. And once the window is full, the request fails.
So the goal isn't to fit everything in. The goal is to fit the right things in.
Anthropic publishes four patterns for managing context in long-running agents. Three are first-class API features, and one is a design pattern.
Don't load everything upfront. Load what the agent needs now, and let it pull more in via tools when it asks.
Think of a compliance review agent. It doesn't get the entire building code book stuffed into its system prompt — it calls a lookup_building_code tool when it needs a specific section. This is the design pattern of the four: nothing special in the API, just a deliberate choice about what you load and when.
When a conversation runs long, Anthropic's server-side compaction summarizes old turns into a single block. You opt in by adding a context_management key to your request, holding an edit with a type:
response = client.beta.messages.create(
betas=["compact-2026-01-12"],
model="claude-opus-5",
max_tokens=1024,
context_management={
"edits": [
{"type": "compact_20260112"}
]
},
messages=messages,
)
The API auto-summarizes when the input crosses the trigger threshold. You don't have to track conversation length yourself.
Prompt caching lets you mark the stable parts of a request — the system prompt, the tool definitions, a long document — and reuse them across calls at a fraction of the cost.
Iniciar sesión unirse a la discusión
The math matters more than it looks. If your system prompt is 4,000 tokens and you call it 100 times an hour, caching is the difference between a usable bill and a phone call from finance.
Some context needs to survive across sessions: user preferences, the agent's running notes, what was decided last week. The recommended primitive for this is the memory tool.
Here's how it works:
In a production app, you'll usually layer all four at once. The compliance review agent caches its system prompt and tool definitions, and pulls building code sections in just in time via lookup_building_code.
Each pattern handles a different failure mode: cost, window size, statelessness. Pick the ones that match what's breaking for you.
context_management key, and the API summarizes old turns automatically when input crosses the trigger threshold.