Agents can merge low-risk pull requests without asking you

October 24, 2026 New Feature

Agents can now merge low-risk pull requests without asking you. When a Project allows it and the implementing agent's Merging pull requests action is Automatic, a pull request that the merge risk assessment rates Low skips your Inbox and goes straight to delivery. We built it because small, low-risk changes waited in your Inbox like every other pull request.

Project settings with the Require human review of pull requests switch turned off

Choose which pull requests skip your review

Every Project starts with Require human review of pull requests on, so pull requests still wait for a person, including those that an agent reviewer used to approve and merge alone. Turn the switch off in the Project's Settings under Git. People with project-management permission can change it, and agents cannot, even by proposal. With it off, a person still decides unless all of these hold:

The merge risk assessment finished and rated the pull request Low, with no category rated High risk.
The implementing agent's Merging pull requests action is Automatic.
The pull request is not one of that agent's periodic spot checks.

When they hold and a person is the assigned reviewer, Task Machine approves the exact commit, adds "Approved pull request #128 automatically" to the Task's activity, and returns the Task to the agent for delivery. When an agent is the assigned reviewer, it reviews as before.

Let agents earn automatic merging

Merging pull requests is its own action on each agent's Autonomy page. Supervised and Balanced agents ask first, Autonomous and Full autonomy agents are Automatic, and Custom sets it on its own. Your approvals and requested changes on pull requests count toward the learned autonomy of the agent that implemented them. Automatic approvals never do.

See why a pull request reached you

When a pull request reaches your Inbox because a condition did not hold, the decision now says why: the Project requires review, the assessment could not run or rated the change too risky, the agent still asks first, or it was picked as a spot check. When the assigned reviewer is an agent or cannot decide, the decision goes to the Task's creator, its Team lead, another person in that Team, the Goal lead, or the workspace owner, in that order. Agent questions and approval requests that name no one follow the same order, starting with the Task's human reviewer.

Keep every existing merge safeguard

An approval belongs to one commit, and a new commit starts the review over. The merge still waits for passing checks, a mergeable pull request, and source-host approval where your repository requires it. The merge command for the approved commit is not held as a separate production change, and any other merge command is checked as before. Tasks that a person implements work as before.