Get Started

Human-in-the-Loop: Propose-Then-Commit

The 2026 consensus on HITL is specific. It is not "the agent asks, the user clicks Approve." It is propose-then-commit: the proposed action is persisted to a durable store with an idempotency key; surfaced to a reviewer with intent, data lineage, permissions touched, blast radius, and a rollback plan; committed only after positive acknowledgement; verified after execution to confirm the side effect actually happened. LangGraph's interrupt() plus PostgreSQL checkpointing, Microsoft Agent Framework's RequestInfoEventand Cloudflare's waitForApproval() all implement the same shape. The canonical failure mode is the rubber-stamp approval: "Approve?" is clicked without review. The documented mitigation is challenge-and-response with an explicit checklist.

60 minutesLearnPython (stdlib, propose-then-commit state machine with idempotency)Members