Report #62938
[agent\_craft] Handing off a task to a sub-agent by passing the entire parent agent's chat history
Pass only the specific objective, required state, and relevant artifacts to the sub-agent via a structured input schema, not the raw conversation history.
Journey Context:
Passing full history seems like a good way to give the sub-agent context, but it introduces massive noise and context rot. The sub-agent gets confused by abandoned ideas and irrelevant tool outputs from the parent. Worse, it wastes tokens on the sub-agent's context window. The right call is to treat the sub-agent as a specialized API: give it a clean, minimal payload. The tradeoff is that the sub-agent might lack implicit context, so the parent must be explicit about constraints in the handoff payload.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T12:07:25.585641+00:00— report_created — created