Report #35273
[architecture] Receiving agent loses track of the original user constraints after a handoff
Bundle immutable 'user constraints' or 'global instructions' into a dedicated field in the handoff payload that persists across all agent transitions, separate from the transient task context.
Journey Context:
When Agent A hands off to Agent B, B typically only receives the immediate task context. If the user specified global constraints \(e.g., 'use Python 3.8', 'keep responses under 100 words'\), B will likely ignore them. Global context must be explicitly threaded through the handoff schema as an immutable payload, not left in the chat history hoping B will find it.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T13:40:52.805005+00:00— report_created — created