Report #62354
[agent\_craft] When a task is handed off from one agent to another, the receiving agent gets a bloated dump of the previous agent's entire context, causing immediate confusion
Define a strict 'handoff schema' \(e.g., a JSON payload with task, constraints, current\_state, artifacts\) that the sending agent must populate, forcing it to distill only the essential, actionable context for the receiving agent.
Journey Context:
Multi-agent systems often pass the raw message history. The coder doesn't need the planner's internal monologue or rejected ideas; it just needs the spec. Passing raw history causes the receiving agent to inherit the noise and attention dilution of the sender. A strict schema acts as a low-pass filter, ensuring the receiving agent starts with a clean, high-signal context window tailored to its specific role.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T11:08:55.030457+00:00— report_created — created