Learn Before
Per-Run State Persistence, Recovery, and Stop Hooks - Engineering Deterministic Runtimes and Verification for Autonomous Agents @ University of Michigan - Ann Arbor
Operational Run Situations in StateM
Stop Hooks and Premature Termination Mitigation - Runtime Verification and Failure Mitigation in Autonomous Agent Workflows @ University of Michigan - Ann Arbor
Runtime Persistence, Recovery, and Stop Hooks - Autonomous Agent Control Planes: State Scaffolding and Resilient Execution @ University of Michigan - Ann Arbor
StateM Stop Hook Integration and Execution Continuation
StateM provides host-level stop-hook integration for command-line interface (CLI) agents (such as Codex and Claude Code) to mitigate premature termination during extended, unattended workflows. When the host environment receives a stop request, the hook intercepts the signal and inspects the current StateM runtime status:
- Permitted Exit: If the execution is in a designated terminal state or is explicitly paused on an external dependency, the stop request is allowed to proceed.
- Enforced Continuation: If the run is in an active, non-terminal state, the stop hook blocks termination, returns the current execution phase alongside outstanding unmet obligations to the agent, and instructs it to continue execution.
Operational Bounds and Guarantees: A stop hook increases execution persistence and enforces an explicit stopping condition, but it does not expand the underlying model's reasoning capabilities or guarantee eventual task success. Because an agent may remain unable to satisfy exit checks, exhaust its resource budget, or loop through ineffective repairs, stop-hook execution must remain constrained by explicit time, token, and retry limits.
0
1
Tags
Prep Sessions
Engineering Deterministic Runtimes and Verification for Autonomous Agents @ University of Michigan - Ann Arbor
Ch.2 Runtime Lifecycle and State Management - Engineering Deterministic Runtimes and Verification for Autonomous Agents @ University of Michigan - Ann Arbor
Per-Run State Persistence, Recovery, and Stop Hooks - Engineering Deterministic Runtimes and Verification for Autonomous Agents @ University of Michigan - Ann Arbor
Runtime Verification and Failure Mitigation in Autonomous Agent Workflows @ University of Michigan - Ann Arbor
Ch.1 Execution Lifecycle and Fault Management - Runtime Verification and Failure Mitigation in Autonomous Agent Workflows @ University of Michigan - Ann Arbor
Stop Hooks and Premature Termination Mitigation - Runtime Verification and Failure Mitigation in Autonomous Agent Workflows @ University of Michigan - Ann Arbor
Autonomous Agent Control Planes: State Scaffolding and Resilient Execution @ University of Michigan - Ann Arbor
Ch.1 Execution Lifecycle and State Boundaries - Autonomous Agent Control Planes: State Scaffolding and Resilient Execution @ University of Michigan - Ann Arbor
Runtime Persistence, Recovery, and Stop Hooks - Autonomous Agent Control Planes: State Scaffolding and Resilient Execution @ University of Michigan - Ann Arbor
Related
StateM Stop Hook Integration and Execution Continuation
Shared Control and Privilege Boundaries in Runbook Modification
Checked and Recoverable Transition Semantics
StateM Per-Run Execution Record
Recovery Anchor and Recovery Scope in StateM
Operational Run Situations in StateM
In StateM, an agent halted in a non-terminal state due to an unresolved human approval is classified as Complete.
According to StateM, what operational situation does an agent run occupy when it is executing within a non-terminal state and progressing through phase obligations?
Discuss the consequences in StateM of treating an execution halt in a non-terminal state as a complete run. What specific criteria does StateM enforce to prevent this error?
StateM strictly separates paused runs from completed runs to prevent temporary blockages from being misclassified as valid ___.
Order the progression of operational situations an agent run experiences as it executes, encounters an unresolved condition, and ultimately finishes its task.
StateM Stop Hook Integration and Execution Continuation
Evaluate the agent run under StateM operational rules. Identify the correct operational situation the run currently occupies, explain why marking it Complete is invalid, and describe the risk this distinction prevents.
A deployment agent in StateM reaches its designated terminal state after finishing its scheduled tasks. However, a post-execution check mandated by the state's exit verification contract fails. How does StateM classify this run?
Match each StateM operational situation to its corresponding execution state and behavior.
Operational Run Situations in StateM
StateM Stop Hook Integration and Execution Continuation
StateM Per-Run Execution Record
StateM Stop Hook Integration and Execution Continuation
Recovery Anchor and Recovery Scope in StateM
Operational Run Situations in StateM
Checked and Recoverable Transition Semantics
Learn After
Under which condition does the StateM stop hook permit a termination instruction to proceed?
Integrating StateM stop hooks provides an absolute correctness guarantee for CLI agent executions.
When halting a premature termination request, what two items does the StateM stop hook return to the agent alongside the continuation request?
Explain why host environments must enforce time, token, and retry limits when utilizing StateM stop hooks for unattended CLI agent execution.
Match each StateM integration concept with its corresponding description.
Place the steps in the correct order for how a StateM stop hook processes a termination signal.
While a StateM stop hook increases execution persistence, it does not expand the underlying model's ___ capabilities.
Identify the specific execution failure the team is experiencing, and explain how integrating StateM at the host level resolves this issue during unattended workflows.