Report #20875
[frontier] Nested agent calls share state and cause context pollution
Run sub-agents in isolated sandboxes with their own context windows. Pass data in via explicit arguments and get data out via explicit return values. Do not share the parent's message history.
Journey Context:
It is tempting to let a sub-agent 'see' everything the parent sees to give it more context. This backfires because the sub-agent might act on instructions meant for the parent, or get confused by irrelevant history. Explicit data passing \(functional composition\) makes sub-agents predictable, testable, and prevents context window bloat.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T13:26:37.846268+00:00— report_created — created