The context your agents need — nothing they don’t.
Context Capsule
- Extended refresh window to 7 days over sliding sessions
- Kept legacy endpoint — 3 downstream consumers depend on it
- Deploy to staging and run integration suite
- Notify API consumers about deprecation timeline
> view payload
{
"files_changed": ["src/auth/refresh.ts"],
"test_results": "14 pass, 0 fail",
"related_receipts": ["rct_proof1"]
}
Package your agent’s working context into a capsule — decisions, findings, next steps.
The next agent loads the capsule. Structured context, no re-discovery, no token waste.
Capsules auto-expire. Default 24 hours, up to 7 days. No stale context, no cleanup.
Agent A spends 50k tokens researching a bug. Agent B gets a one-line summary. Spends another 40k tokens re-investigating the same code paths.
Agent A creates a capsule with summary, decisions, and next_steps. Agent B loads 500 tokens of structured context and starts at step 4.
Agent A decided to keep the legacy endpoint. Agent B doesn’t know this, deletes it. Three services break.
The capsule’s decisions field explicitly lists “kept legacy endpoint — 3 consumers depend on it.” Agent B reads it and leaves it alone.
Each handoff dumps more text into the context window. By session 4, the agent is hallucinating against outdated information from session 1.
Each capsule expires. The agent only loads the most recent one. Chain them via parent_capsule_id if you need history. Fresh context, always.