A task's status shows where it stands on the journey from description to pull request.
| Status | Meaning |
|---|---|
PENDING | Accepted, waiting for an available agent slot. |
IN_PROGRESS | Currently being worked on. |
PENDING_REVIEW | Work is finished and reviewed; now awaiting integration or approval. |
COMPLETED | Delivered |
NEEDS_HUMAN_REVIEW | Coroid cannot proceed alone and needs your input. |
PAUSED | Temporarily paused and can be resumed later. |
FAILED | Execution could not be completed. |
CANCELLED | Stopped by you. |
WONT_FIX | Closed deliberately without carrying out the work. |
PENDING
Queued. The task is valid and waiting for capacity.
If it remains in this state longer than expected: all your slots are occupied, or higher-priority tasks are ahead of it. Check priority (P0 to P3) and
capacity. Adding more slots shortens the queue; it does not speed up tasks already running.
IN_PROGRESS
An agent is currently working on it. You can watch the process live.
If it takes longer than similar tasks: usually due to a slow or hanging test suite, or a specification that is too broad, causing the agent to keep finding more work to do. See When a task gets stuck or fails.
PENDING_REVIEW
The work is built and has passed an automated review. It is now waiting for integration or your approval.
What to do: review the pull request. See Review and merge the result.
COMPLETED
Delivered. For most tasks, this means the pull request is open and ready; merging remains your responsibility.
NEEDS_HUMAN_REVIEW
This is not a failure. The task reached a point requiring a human decision — an ambiguous requirement, two equally valid approaches, a missing credential, or an unstated constraint.
What to do: read the question, provide an answer, and the task will continue from where it paused. A precise answer is better than a vague one; otherwise, the agent will guess again.
If you see this status frequently, the usual cause is poorly specified work. See Specifications.
PAUSED
Stopped intentionally and can be resumed later. Its slot is freed while paused.
FAILED
Execution could not be completed. This differs from work that ran but did not pass — that results in rework or findings.
Common causes:
- build or test commands that do not work in a clean workspace
- a missing dependency, credential, or service required by the suite
- the repository connection losing access mid-run
- the task exceeding a run limit on your plan
What to do: read the failure output, which identifies the stage that failed. Most first-time failures relate to environment configuration — see Build and test configuration.
CANCELLED
You stopped it. The run halts and the slot is freed immediately.
WONT_FIX
Closed deliberately without doing the work — already resolved, not applicable, or decided against. This differs from CANCELLED in intent: WONT_FIX is a judgement about the work, CANCELLED is a judgement about the run.