Bind the request to the action
The compatible runner submits a safe title and a digest of its local action snapshot. Review the proposed operation against that local record before approving it.
04 / CONTROL
Put a decision before the action.
Add human approval to specific agent actions with digest-bound, single-use authorization and cooperative SDK checkpoints.
WHY IT MATTERS
An approval should describe what it permits.
For consequential operations, a broad instruction to proceed is not enough. Integrate a guarded action so the runner requests a decision tied to the exact operation it intends to perform.
RUN HISTORY
Weekly research brief
Reported complete- Collect sources
- Reported
- Draft the brief
- Reported
- Human outcome review
- Awaiting review
An agent reports completion. Your team decides whether the result meets the brief.
Consume authorization once
A compatible runner consumes the approved authorization before executing that guarded operation. Changed parameters require the corresponding authorization; an approval is not a blanket permission slip.
Pause at a real checkpoint
Pause, resume, and cancellation are cooperative. Your runner needs compatible checkpoints to receive and handle the decision. Requested and acknowledged states mean different things.
START WITH ONE WORKFLOW
Put your next run
under supervision.
Connect the agent you already run. Build confidence from the work you can actually review.