In multi-agent orchestrator loops, a single inter-agent message body can get serialized into two places at once: the replayed conversation history AND the tool-result blocks. You then re-pay input tokens for the same payload twice on every replayed turn, and the waste compounds as the thread grows. Store each message once and reference it by ID so the duplicate disappears — a structural fix, not an after-the-fact prune (shipped in Claude Code 2.1.212).
Store Each Inter-Agent Message Once, Then Reference It
🔒 Pro tip · Advanced
Unlock this tip — and 105 more
This is one of 106 advanced, fact-checked tactics reserved for Pro. Get the full 128-tip library, a searchable archive, and a new tip every morning. Free for 7 days, then $9/mo.
Prefer to browse? The 22 Beginner tips are free forever.
More in Context Management
🧠Context Management
Images can be 1,000-2,000+ tokens each; removing stale ones cuts that per turn
Drop the Screenshot Once the Model Has Read It
Images, PDFs, and attachments are charged as tokens and re-sent every turn in a multimodal thread. After the model has described or transcribed one, you usually don't need to keep sending the pixels.
🧠Context Management
50-90% on file-heavy prompts
Paste the Function, Not the Whole File
Most coding questions need 20-40 lines, not your 800-line file. Send the relevant slice plus a one-line note about the rest, and your input shrinks dramatically without hurting the answer.
🧠Context Management
Trims re-sent history; often 20-60% fewer input tokens per turn after a topic switch
Start a New Chat When the Topic Changes
Chat apps re-send your whole conversation with every message. When you switch tasks, the old turns become dead weight you keep paying to re-transmit — even with caching discounts.