Expand description
Resuming an attempt a killed process left behind.
Before an attempt, a marker records its admission key, the checkpoint it
started from and the acceptance tests it is judged by. A run that ends in
any ordinary way removes it (Guard); a killed process cannot, so a
marker on disk means an attempt was interrupted. The next run then keeps
the worktree as the attempt left it and admits the attempt under the same
key: agentplane finds the interrupted run and resumes it from its journal
— model calls and tool calls that finished are read back, not repeated —
and a run that had already finished is read back whole and judged again
(a task that passed just before the kill is ticked now).
Structs§
- Guard
- Removes the marker when a task run that started an attempt ends in any ordinary way. A run refused before its attempt starts (a session check, a worktree held by a waiting call) leaves an interrupted or waiting attempt’s marker alone: that attempt still resumes.
- Marker
- An attempt in progress.