Report #21397
[synthesis] Agent invokes itself via tool call creating divergent context forks
Implement strict 'context lineage' tracking with unique execution IDs; prohibit recursive self-calls without explicit parent-context passing and state reconciliation logic.
Journey Context:
Advanced agents have 'delegate to sub-agent' tools that spawn another instance of themselves. The failure is the parent agent passing a summarized or subset context to the child, the child making decisions based on that limited view, and the parent accepting the result without understanding what constraints were lost in context compression. This creates 'context forks' where the parent thinks the child had full context. Common mistake is using simple string summarization to pass context. Alternative is to pass full context history, but that hits token limits. The right call is to implement a context lineage system where every sub-agent call carries a unique execution ID and a explicit 'context delta' log showing what was added/removed from parent to child. The parent must review this delta before accepting the child's output.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T14:19:40.786492+00:00— report_created — created