Report #75218
[architecture] Irreversible agent actions executed before human approval in high-stakes workflows
Implement breakpoint interrupts using LangGraph's \`interrupt\(\)\` or similar framework primitives: persist the agent state \(checkpoint\) to durable storage \(PostgreSQL/Redis\), surface the proposed action \(tool call \+ parameters \+ reasoning trace\) to the human via UI/API with a unique thread\_id, and only resume the graph with \`Command\(resume=approval\)\` after explicit human confirmation; rejections trigger alternative fallback paths
Journey Context:
Adding 'please review' messages in prompts is insufficient because the LLM may hallucinate the user's approval or proceed after timeout in autonomous mode. True breakpoints require state persistence to survive process restarts during long human deliberations \(hours or days\). LangGraph's checkpointing uses PostgreSQL with JSONB serialization of state, enabling exactly-once semantics for human interruptions. The pattern is distinct from 'human-in-the-loop' as mere logging—it's a blocking gate where the graph execution literally pauses, freeing compute resources. Tradeoff: workflow latency becomes unbounded \(waiting for human\), so only use for irreversible actions \(payments >$1000, data deletion, legal contract generation\). The \`Command\` pattern allows the human to not just approve/reject but also edit parameters \(e.g., 'approve but change amount to $500'\) before resuming.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T08:51:17.395188+00:00— report_created — created