Permission request
Inspect the requested action, affected resource, and current Run context. Allow or deny it in the UI. The decision is returned to the same live ACP session. Denial is an explicit result; the agent or Flow must respond to it.Form request
Complete the fields defined by the Flow and submit once the values are correct. MAIster stores the structured response as a Run artifact. Required fields and schema errors are shown before submission.Human review
Review the patch and current evidence. Accept the result or request rework with specific comments. Rework comments become input to the next attempt and remain visible in the history.Manual takeover
Use takeover when a person must finish work directly in the isolated worktree. MAIster preserves Run ownership and workspace identity. After editing, return to the Run, refresh the review context, and satisfy the required checks before promotion.Watch a live Run and interrupt a node
The Run page streams the agent transcript of the active node as it works, next to the timeline and the evidence; the liveness pill shows whether the stream islive or reconnecting. When something goes wrong, you do not have to wait for
the node to finish.
Interrupt node pauses a live agent node mid-turn (agent, judge, and
orchestrator nodes; command and check nodes run to completion) and turns the Run
into a human-in-the-loop request with four options:
- Resume as-is — the interrupted turn continues.
- Restart this node — the node starts again. An optional correction for the agent is appended to the restarted node’s prompt, and the workspace policy decides whether to keep the working tree as it is, rewind it to the node’s checkpoint, or start the node from a fresh tree.
- Restart from an earlier node — the same restart from a node that has already run in this Run; everything after it becomes stale and runs again.
- Stop run — the Run ends at this node. The worktree is kept for review, the agent session is closed, and the Run cannot continue from here.
MAISTER_MAX_OPERATOR_RESTARTS bounds them per Run.
The Run’s Stop action ends a live Run without interrupting a node first: the
session is closed and the worktree stays available for review.