Skip to main content
A run is a record of one request against one immutable published workflow revision. Open the project Runs area to inspect active and past work. A run preserves earlier attempts and committed workflow events so people can see what changed and who reported it.

​
Read a run

The current run projection includes the pinned workflow ID and revision, run status and version, current candidate and plan revision, step graph, current and previous attempts, recorded check results, and actor-specific nextActions. Run status is active, blocked, completed, or cancelled. Each graph node shows its status, predecessor, instructions, eligible actor kinds and roles, required outputs, acceptance rule, current attempt ID, and attempt history. An attempt records its state, performer if assigned, outputs or blocker, handoff notes, and whether earlier evidence has been superseded. The candidate is the exact reference submitted by Implement. Verification and independent review attach to that candidate, Plan revision, implementation attempt, and their own current attempts. A new candidate or Plan revision means older candidate-dependent results remain visible as history but no longer satisfy the gate.

​
Available actions

The nextActions list is calculated for the authenticated actor and current run state. It may include start_step, submit_step, decide_step, report_blocker, handoff_step, report_check, request_rework, and cancel_run. Treat this list and the node’s currentAttemptId as current state; do not infer permission from a role label or an earlier response. An MCP run mutation returns the updated run projection and a receipt identifying its command and recorded event. MCP get_run returns a run projection and eventCursor; it does not return an unfiltered event array. The cursor marks the event position represented by that projection.

​
Event history

Use Logs to inspect recorded project events and follow an event to its run. Project event filters include run ID and event type. The MCP get_run eventCursor refers to the events represented in that projection; use the hosted Logs area for browsing project history. Events are committed workflow reports and transitions. They are not a full server log or a passive record of editor activity, prompts, transcripts, or external CI output that was never submitted. For current permissions and execution order, see the Agent guide.