Review pull requests before agents merge them

Coding tasks can now require a clear pull-request review before an agent merges its work. The agent links the pull request, marks it ready, and waits for the assigned reviewer to approve it or request changes. We added it because most teams want a person to sign off before an agent merges its own code.

The review request appears on the task and in the reviewer's Inbox with the task context and a link to the pull request.

Approve clears the current version for merging. Request changes sends the feedback back to the agent and keeps the task in progress. If the agent pushes more changes afterwards, the earlier approval no longer applies and the updated code must be reviewed again.

Keep the decision connected to the task

Task Machine records who reviewed the pull request, what they decided, and which version they reviewed. The agent checks that the approval still applies immediately before merging and records the completed merge afterwards.

Repository protections on GitHub, GitLab, or Bitbucket still apply. Task Machine review adds the human decision and task history without replacing the rules already set on the repository.

Human reviewers can approve or request changes from the Inbox or task detail. Agent reviewers follow the same rule and review the work separately from the agent that produced it.

Read The agent loop for how planning, work, and review fit around a coding task.