Skip to main content
By the end of this guide, when you or someone you trust reviews a pull request you opted in, an agent changes the code to address the feedback, runs your fast checks, pushes a commit to that pull request’s branch and replies in each review thread. A person still approves and merges. This is autopilot-review-responder, one of the Autopilot built-ins. It works in a checkout, so it runs on a machine that holds a clone of the repository.

Before you begin

  • The reliant CLI, v1.21 or later, signed in (Sign in and tokens), and gh for the GitHub side.
  • The Reliant GitHub App on the repository (GitHub integration), and a connected machine with a clone of it in a Reliant project. Turn issues into pull requests sets up the same project and machine.
  • In an organization: an organization AI account that can run the flagship model, the responder’s default.
1

Turn on the review responder

Run this in the clone. --machine takes the machine’s hostname or daemon ID. gate_command is the check that must pass before anything is pushed; the default runs gofmt and your short test tier, so set it for your repository.
terminal
The triggers wake it for a review, an inline comment and a pull request comment. In the app: Workflows → Library → Autopilot · review responder → Set up. Settings: Autopilot settings.
2

Opt a pull request in

The responder only touches pull requests carrying agent:authored, which the issue worker puts on the pull requests it opens, or agent:respond, which you add to any other:
terminal
A pull request from a fork is never pushed to.
3

Check whose feedback counts

Feedback counts only from you, the accounts in trusted_ids, and Autopilot PR review when it has findings. To test that, save the review-submitted filter from the workflow source as filter.cel and evaluate it against a sample event:
terminal
The same event on a pull request labelled only bug prints false.
4

Review the pull request

Leave a review with a body, or comment on a line:
terminal
The newest row should say launched with a chat ID. Follow it with reliant workflow follow <chat> or under Workflows → Runs.
5

Read what it did

On the pull request, look for:
  • a lease comment and the agent:working label while the run holds the pull request;
  • a commit on the pull request’s branch, pushed only after gate_command passed (a run whose changes fail it twice pushes nothing);
  • a reply in each inline thread, and one summary comment for the round;
  • agent:working removed when the round ends.
Feedback that arrives during a round is picked up by another round. After max_review_rounds (3 by default) the pull request is labelled agent:blocked and left to you.
6

Turn it off

Pass --project-id, or deactivate pauses the workflow in every project you own:
terminal

What this does not do

  • It never approves or merges. No Autopilot workflow calls a merge. To merge from a workflow you compose that step yourself (Merging is a workflow step).
  • It pushes only to the pull request’s own branch. Never to the default or a protected branch, never with --force. The agent’s shell has no credentials.
  • It ignores strangers. Feedback from anyone outside trusted_ids starts nothing and never reaches the agent.
  • It has no budget of its own. Each round is up to 80 agent turns, three rounds per pull request, plus a retry. See What it costs.

Troubleshooting

trigger events shows the firing as failed with this detail and no chat: the event passed the filter, but the run could not start. An admin can add an organization API key or turn on Reliant credits, or set --param 'model={"tags":["fast"]}' to a model an organization account can run.
Turning on all three triggers in one call can time out, and then none is enabled. Run the same command once per trigger, adding --trigger review-submitted, then --trigger review-comment, then --trigger pr-comment.
Check that the pull request carries agent:authored or agent:respond, that the review has a body (an approval with no text is not feedback), and that it came from you or an account in trusted_ids.

Next steps

Review every pull request

The AI reviewer whose findings this workflow answers.

Turn issues into pull requests

The issue worker opens the agent:authored pull requests.

Autopilot reference

Labels, leases, settings and costs of every Autopilot workflow.

Who an automation acts as

The Reliant bot, your own account, and the push check behind both.