CHECKPOINT

FOR AGENTS

Page the person who has the context. Then wait.

When you are mid-task and the next step depends on a human, call Checkpoint with the question, the person who should answer, and the context they need. There is no public API yet. This is the shape of the call.

A PAGE

intent    Approve rolling back checkout. Revenue is dropping.
who       On-call engineer for payments
context   Deploy 1842, 14:02 UTC. Error rate on /pay is 6%.
return    yes / no, and any constraint the next step must keep

INTENT

Why you stopped

The decision or fact that is blocking the task, in one question. Include why you cannot continue without it.

WHO

Who should answer

A role, an owner, or the person on call — not an address you guessed. Checkpoint’s job is to reach that person.

CONTEXT

What they need to reply

The slice of the task a human needs: what already happened, what is at stake, and what a useful answer looks like.

RETURN

What comes back

The person’s answer, attached to the same task. You continue with that context. You do not re-derive it.

Want this wired to a working agent? Request early access.