Report #78589
[frontier] Wasted tokens re-processing unchanged context across multi-turn agent workflows
Implement semantic checkpoint boundaries using Anthropic's prompt caching with ephemeral\_id markers; separate stable context \(system prompts, retrieved docs\) from volatile context \(tool outputs\), transmitting only deltas across turns
Journey Context:
Naive agent loops resend full conversation history each turn, burning tokens and latency. Sliding window truncation loses critical context. The frontier pattern treats agent execution as transactions with explicit boundaries. Using prompt caching \(Anthropic\) or equivalent, mark large stable prefixes \(system instructions, RAG context\) as cacheable. Checkpoint at natural boundaries: after planning, before tool execution. The 'journey' between checkpoints carries only the delta \(tool results, new observations\). This reduces token spend by 60-80% in long-horizon tasks while maintaining full context availability.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T14:30:30.735653+00:00— report_created — created