Mission, task & review states — cheatsheet
Quick lookup. For longer explanations, see Lifecycle states.
Mission
The dashboard shows mission statuses exactly as listed here — raw names like InProgress or PendingReview, not spaced labels.
| State | Terminal | What it means |
|---|---|---|
| AwaitingApproval | no | Proposed from a conversation; waiting for your approval before it enters the queue. |
| Pending | no | Created; planning hasn't started yet. |
| Researching | no | Background research before decomposition is running. |
| Planning | no | The mission is being planned (research + decomposition). |
| Decomposing | no | The planner is actively producing the task plan. |
| Decomposed | no | Task plan ready; waiting for your approval before tasks dispatch. |
| InProgress | no | Tasks dispatched and executing. |
| PendingReview | no | Waiting on your review before completion. |
| Paused | no | Paused by you. Resumable — click Resume. |
| PendingOperatorDecision | no | The mission raised a question and waits for your answer on the mission page; nothing moves until you respond. |
| Completed | yes | Done. One sanctioned exit — see below. |
| Failed | yes | Stopped on an error. |
| Cancelled | yes | You stopped it. |
Not every mission passes through every state. The happy path is Pending → Planning → InProgress → PendingReview → Completed (or Failed), with Paused as a resumable side state.
Buttons on the mission page: Pause (while InProgress), Resume (while Paused), Cancel Mission (shown unless the mission is Completed or Cancelled), Approve Decomposition Plan (while Decomposed or AwaitingApproval).
Two rules worth knowing:
- Completed is terminal, with one exception. Starting a fresh run on a completed mission reopens it to InProgress. Nothing else takes a mission out of Completed.
- Illegal state changes are refused, not ignored. If you (or a tool) request a transition the current state doesn't allow, the request fails and the error tells you which actions are legal. A refused change never reports success.
Run outcomes
Runs belong to workflow missions — one run per workflow execution, on its own branch (see Lifecycle states).
| Outcome | Terminal | What it means |
|---|---|---|
| Proposed | no | The only open state: the run's changes wait on their branch for your decision. Outside a competing group, one run may be open at a time. |
| Accepted | yes | You accepted it; the run merged into the mission and produced a changement. |
| Rejected | yes | Declined — discarded via the agent verb, or auto-rejected when a competing sibling was accepted. The run's branch is deleted; nothing landed. |
| Superseded | yes | Replaced by a newer run; no longer in play. |
Task
Coding-task statuses, as they appear on task lists and inside a mission:
| Status | Terminal | What it means |
|---|---|---|
| Pending | no | Approved, queued; not yet handed to a coder. |
| Dispatched | no | Handed to a coder; execution hasn't started yet. |
| InProgress | no | A coder is working. |
| UsageLimitWait | no | Paused on a provider usage limit. Not an error — it resumes on its own when the quota window reopens. |
| Completed | yes | Done; result on the review mirror. |
| CompletedNoPush | yes | The coder finished cleanly but had no changes to push. |
| TurnLimitReached | yes | The coder used up its turn budget before finishing. The task can be resumed with additional turns and continues where it stopped. |
| Failed | yes | Errored out. Check the task log; the ↻ button ("Retry task") resets it to Pending for another attempt. |
| Cancelled | yes | Stopped by you or by mission cancel. |
Review
Review statuses appear raw, like the other tables (InReview, not "In review"):
| State | Terminal | What it means |
|---|---|---|
| Pending | no | Review created; nobody has picked it up yet. |
| InReview | no | The review is open and being looked at. |
| Approved | yes | You approved. Push to origin is in flight or done. |
| Rejected | yes | Dropped. Branch stays on mirror but never pushed. |
| Cancelled | yes | Called off before a decision. Nothing is pushed. |
Request Changes is a button, not a state: on a mission review's decision card (Reviews dashboard) you can Approve, Request Changes, or Reject — the review record itself only ever holds one of the five states above.
Review Engine finding
Findings inside a review have their own status:
| Status | What it means |
|---|---|
| Open | Fresh, not triaged. |
| Investigating | You marked it as being looked at. |
| Resolved | Fixed (manually or by a follow-up coder task). |
| Dismissed | You decided it's not a real issue. |
| Deferred | Push to a future run. |
Attention request
Attention requests don't have a state per se — they're either outstanding (waiting on a human) or resolved (a human responded). They appear on the mission page and trigger an email.
Types you'll see:
- Approval — "approve this plan/change to continue".
- Decision — "pick one of these options".
- Input — "give me a string / a value to use".
- Clarification — "your brief was ambiguous; please resolve".
- Error — "something failed; please intervene".