PR Auto-fix
Review comments and red checks, handled
Once the agent opens or links a pull request, Auto-fix watches its checks and review threads. When feedback lands, the agent picks the work back up in the same thread, pushes to the same branch and keeps going until everything is green.
Definition
What Is A Pull Request Review Loop?
A review loop is a coding agent that stays attached to its pull request after opening it. Instead of handing the PR over and forgetting it, the agent responds to failing CI and reviewer comments until the PR is ready to merge.
In Hoplite, the loop is called Auto-fix. It is on by default for GitHub pull requests, it runs each fix pass in the thread that wrote the code, so the agent keeps the full context of why the code looks the way it does, and every pass is visible in that thread.
Watches the PR
Checks And Reviews, Seen As They Land
Auto-fix listens to GitHub for check runs, commit statuses, reviews, review comments and review threads on the pull request, and re-checks unfinished CI every few minutes in case an event was missed. Feedback that arrives mid-pass is queued for the next one.
Same thread, same branch
Fixes From The Agent That Wrote It
Each pass is a new run in the original thread. The agent reads the failing checks and open review threads, makes the fix, pushes to the pull request's branch and resolves the review threads it addressed. If a reviewer replied in the meantime, the thread is reopened.
Trusted feedback only
It Listens To Your Team, Not Strangers
Only feedback from workspace members, collaborators with access to the repository, and a short allowlist of review bots (Greptile, CodeRabbit, Copilot's reviewer and Sentry) can start a pass. Comments from anyone else, including other bots, are ignored.
Knows when to stop
Green, Merged, Or Asking For Help
The loop settles when every check is green and nothing is left to address, and switches off when the pull request is merged or closed. If a pass makes no progress on the same feedback, it stops and asks for your input. Merge conflicts get up to three automatic attempts.
Comparison
By Hand Vs. Auto-fix
| Question | Fixing feedback by hand | Hoplite Auto-fix |
|---|---|---|
| Noticing a red check | When someone looks at the PR | A GitHub event wakes the agent |
| Review comments | Read, switch branches, fix, push | Fixed and resolved in the same thread |
| Merge conflicts | Rebase by hand | Up to three automatic attempts |
| Context | Rebuilt from the diff | The thread that wrote the code |
| When it stops | When you get to it | All green, merged, closed, or stuck and asking |
| Merging | Someone clicks merge | Optional auto-merge once checks settle |
FAQ
Auto-fix, Answered
- How do I turn Auto-fix on?
It's on by default. Workspace owners set the default in workspace settings, projects can inherit or override it, and each pull request has its own Auto-fix switch in the thread. Turning it off for a PR keeps it off.
- Which pull requests does it work on?
Open GitHub pull requests that the agent created or that were linked to a thread. Each PR gets its own loop, so a stack of pull requests is handled independently.
- Whose comments does it act on?
Hoplite workspace members, repository collaborators with access, and the Greptile, CodeRabbit, Copilot pull request reviewer and Sentry bots. Everything else is ignored.
- Can it loop forever?
No. It stops when the pull request is green, merged or closed, and it stops to ask for input when a pass makes no progress on the same feedback. Each pass also runs under a time budget.
- Will it merge my pull request?
Only if you turn on auto-merge, which is off by default. It waits for required checks and any Auto-fix work to settle, then merges with a method the repository allows.
- Does it work with GitLab or other providers?
Not yet. Auto-fix is GitHub-only today; other providers still show synced pull request state in the thread.
Ship pull requests that finish themselves
Connect a GitHub repository, start a thread and let Auto-fix carry the PR to green. Try Pro free for 14 days.