desktop

Stay in control of a run

Inspect, steer, stop, resume, or retry Desktop work without throwing away its history.

DesktopbeginnerCurrent releases
Verified 2026-08-04View sourceReport a docs issue

Steering, stopping, resuming, and retrying remain recorded in the same session as the work they affect. You can change course without losing the history that led to the decision.

Read the current state

Distinguish running work from waiting, blocked, failed, cancelled, and completed outcomes. Read the focused project/session, active attempt, exact waiting request, last terminal result, and any uncertain external effect before choosing an action.

Choose the right action

What you seeActionWhat happens
The run is healthy but taking the wrong approachSteerAdds guidance to the active work
The run should not continueStopCancels execution and records the decision
Kestrel is waiting for a choice or missing valueResumeSupplies the requested response to the same run
A completed or failed attempt can safely be repeatedRetryStarts another attempt with the same session context

Before acting, read the focused session, active run, wait reason, and last terminal outcome. After acting, confirm that the new event appears in the same session.

Answer an exact decision

Submit the pending request and registered option identifiers shown by Desktop. A response for another request, session, actor, or stale state is rejected rather than guessed.

Control Mission Control work

Run actions steer execution. Mission Control actions inspect or change project work, attempts, evidence, review, and acceptance. Use the surface that owns the desired state.

Verify the action

Confirm the same session records the operator action and subsequent state. A resume should continue the original pending work; a stop should reach a truthful cancelled terminal outcome.