Review agent work

Review the output of an agentic job and decide whether to approve or send it back for revision.

When review happens

After an agent finishes working on a repository-context job, it opens a pull request. The job moves to Awaiting Review.

You receive a notification and can review the work.

Review in Coord

1. Open the job from your workspace board or activity view.
2. The job detail panel shows:
   • The agent's work summary
   • A link to the pull request
   • Artifacts produced during execution (logs, screenshots, output files)
   • Notes and history from the current and previous attempts
3. Review the changes and choose an action:
   • Approve — opens the approval dialog where you choose what happens to the pull request (see Approving below).
   • Request Changes — describe what needs to be different. The agent starts a new attempt using your feedback.

You can also view the pull request diff directly in the job detail panel without leaving Coord.

Review on GitHub

You can also review the pull request directly on GitHub:

1. Open the pull request link from the job detail panel.
2. Review the code diff (the comparison showing what changed), leave comments, and submit your review.
3. Coord syncs your GitHub review back to the job — if you approve on GitHub, the job reflects it in Coord, and vice versa.

The revision cycle

When you request changes:

1. The agent receives your feedback along with full context from previous attempts.
2. A new attempt begins. The agent addresses your feedback and pushes updates to the same pull request.
3. The job returns to Awaiting Review for another round.
4. This cycle repeats until you approve.

Each round of work is a separate attempt, giving you a complete history of how the work evolved.

Approving

When you approve a job, the approval dialog lets you choose what happens next:

• Ready PR — convert the draft pull request to "ready for review" on GitHub.
• Merge PR — merge the pull request after CI checks pass. Requires Ready PR.
• Delete branch — remove the branch after merging.
• Close issue — close the linked GitHub issue.

If CI (continuous integration — automated checks like tests and builds that run when code changes are proposed) checks are still running, Coord monitors them in the background and merges automatically once they pass. You can close the dialog — the approval continues in the background.

Updating the pull request branch

If the pull request is behind the base branch (for example, other changes were merged while the agent was working), you can update it from the job detail panel. Coord merges the latest base branch into the pull request branch so CI checks run against the most recent code.

When something goes wrong

If CI checks fail after you approve, Coord pauses the approval. You can:

• Request changes — send the job back to the agent with feedback about the failure.
• Approve anyway — mark the job as done without merging.
• Cancel approval — return the job to Awaiting Review and optionally convert the pull request back to a draft.

If the merge is blocked by branch protection rules or required reviews on GitHub, Coord shows a warning. Resolve the issue on GitHub, then retry the merge from Coord.

No-code-change jobs

Sometimes an agent completes work without making code changes. In this case, no pull request is created. You can still approve the job to move it to Done, and optionally delete the working branch.

Next steps

• Reviews and attempts — deeper look at the review cycle
• Set up GitHub integration — connect your repositories
• Create your first job — create a job to review