When one agent works a big fan-out job - reviewing hundreds of contracts, auditing a repo, cross-checking many sources - in a single thread, every document and every finding piles into one context window that is re-billed on every turn, and long runs drift toward the long-context price cliff. Anthropic's Managed Agents now let the agent write a dynamic workflow: a program that runs many agents in phases in the background as one workflow run, each in a context-isolated thread, with context and results passed programmatically between them. The orchestrator's own thread stays small because it only monitors the run's phase events instead of holding every agent's transcript.
Offload Big Multi-Agent Jobs to a Background Workflow Run So the Orchestrator's Context Stays Flat
🔒 Pro tip · Advanced
Unlock this tip — and 140 more
This is one of 141 advanced, fact-checked tactics reserved for Pro. Get the full 163-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.