Report #27010
[frontier] Implementing human-in-the-loop as a synchronous blocking breakpoint that halts the agent thread
Use asynchronous interrupts with state persistence. The agent pauses, saves its state to a database, and yields control. The human can approve hours later, and the agent resumes exactly where it left off.
Journey Context:
Synchronous blocking requires the human to be watching constantly. If the human is away, the agent hangs and wastes resources \(or times out\). Asynchronous interrupts with checkpointing allow the agent to be completely unloaded from memory. Upon human approval, the agent is rehydrated from the checkpoint, making long-running, human-supervised workflows viable in production.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T23:44:12.653925+00:00— report_created — created