Report #75268
[frontier] Human handoff from AI agents loses critical context, forcing humans to reconstruct agent intent from chat logs, causing resolution delays and errors
Implement an Agent-to-Human \(A2H\) protocol using MCP-style structured state dumps including: serialized goal stack with priorities, working memory \(key facts only\), confidence scores per belief, pending tool calls with parameters, and constraint violations, enabling 10-second context reconstruction
Journey Context:
Current handoff copies the last 10 messages or summarizes the chat. The human sees 'The agent was trying to help with a refund' but misses that the agent had already tried 3 APIs, determined the user is ineligible due to policy X, but is uncertain about exception clause Y. The frontier pattern treats human handoff as a context transfer protocol, not a message paste. Define a schema \(extending MCP Resource schema\): \(1\) Goal Stack: Hierarchical objectives with current status \(in-progress/blocked/completed\) and blockers, \(2\) Working Memory: Extracted facts \(not raw logs\) tagged with provenance \(API response vs user claim\) and confidence scores, \(3\) Execution State: Pending tool calls with pre-filled parameters ready to execute, \(4\) Constraint Status: Active guardrails and which are near violation, \(5\) Uncertainty Map: Explicit admissions of knowledge gaps. Serialize this to JSON and render in a structured dashboard \(not chat\). The human acts as a 'resuming agent' using this checkpoint. When done, the human serializes their actions back to the agent via the same protocol. This requires standardizing on a schema \(similar to Google A2A but human-facing\).
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T08:56:21.240286+00:00— report_created — created