Reviews and attempts

When an agent finishes working on a job, the result goes through a review before it is marked as done. This ensures quality and gives you control over what gets shipped.

The review cycle

For agentic jobs that work on a repository:

The agent finishes its work and opens a pull request.
The job moves to Awaiting Review.
You review the changes. You can look at the pull request on GitHub or review directly in Coord.
You choose one of two actions:
- Approve — the changes are merged and the job moves to Done.
- Request changes — you describe what needs to be different. The agent receives your feedback and starts a new round of work.

When you approve, Coord handles the merge process in the background. If your repository requires checks (automated tests or builds) to pass before merging, Coord waits for those checks and then merges automatically. You will see status updates during this process — if checks fail or the merge is blocked, Coord lets you know so you can take action.

In some cases, a repository-context agent may complete without producing a pull request — for example, if it determines no code changes are needed. You can still approve the job to mark it as done.

For agentic jobs that run locally (without GitHub), the agent completes and the job moves directly to Done. There is no pull request to review.

For user jobs, you complete your own work and mark the job as done.

What is an attempt?

An attempt is a single round of work on a job. Every time an agent or person works on a job, that is one attempt.

The first time work begins, that is attempt 1.
If you request changes during review, the revision is attempt 2.
Each additional review cycle creates a new attempt.

Attempts are numbered sequentially and each one is recorded with its own notes, artifacts, and outcomes. This gives you a complete history of how the work evolved.

Review flow for repository jobs

Agent works (Attempt 1)
    ↓
Pull request created
    ↓
Awaiting Review
    ↓
┌─ Approve → Merge → Done
└─ Request Changes → Agent works (Attempt 2) → Pull request updated → Awaiting Review → ...

When you request changes, you can include specific feedback describing what needs to be different. The agent uses this feedback — along with the full context of previous attempts — to address your concerns.

Updates from revision attempts push to the same pull request, so reviewers always see the latest state of the work.

Stopping an agent early

If you want an agent to stop before it finishes on its own, you have two options:

Stop — the agent wraps up its current task and preserves all work done so far. The job moves to Awaiting Review (for repository-context jobs) or Done (for local-context jobs), so you can review what was completed. Use this when you want to redirect the agent or when you have seen enough progress.
Cancel — the job is terminated immediately and moves to Canceled. This is permanent — canceled jobs cannot be restarted.

To stop an agent, click the stop button in the session view while the agent is working. To cancel, use the Cancel action in the job header.

Reviewing in Coord vs. GitHub

You can review agent work in two places:

In Coord — use the job detail panel to see the agent's output, leave notes, and approve or request changes.
On GitHub — review the pull request directly on GitHub. Coord syncs review feedback between both surfaces, so your GitHub review comments are reflected in Coord and vice versa.

Jobs — the two job types
Job lifecycle — how review fits into the overall lifecycle
Review agent work — step-by-step guide to reviewing