AI code review on your own provider — including local models.
Configure a supported CLI, a localhost model, or an OpenAI-compatible endpoint. PR Flow sends each AI task to the provider you select; a localhost endpoint keeps the prompt on your machine.
Know where each AI request goes.
Each provider row names its destination before you run a review. Choose a local model, an authenticated CLI, or your own compatible endpoint.
No hosted PR Flow model
PR Flow composes the request on your machine and sends it to the provider you configured.
Someone else's model choice
Select the provider and model for each task, including an approved internal gateway.
Score theater
Findings point to code and estimates remain advisory. The human reviewer decides what is useful.
Bots that act on their own
Findings and discussion answers can become staged comments. They never post autonomously, and they do not approve or merge.
Supported providers, routed per task.
Configure providers under Settings → Integrations → AI providers. Each row names where prompts go and includes a connection test.
Built-in CLIs
The Claude, Antigravity, and Codex command-line tools use their existing authentication.
A local model
Ollama or another compatible service on localhost keeps prompts on your machine.
An OpenAI-compatible endpoint
Supply the URL and key for a compatible service or internal gateway. The key is stored encrypted.
A custom local CLI
Configure a command and prompt argument for a compatible command-line tool.
Task routing: mix them
Route deep review, estimates, thread summaries, Discuss, and summary drafts separately. Results identify the provider and model that produced them.
Findings on lines, not a grade out of ten.
Pins you accept or dismiss.
Findings whose quoted code still matches the file appear as gutter pins. Accept one to create a staged comment or dismiss it. The comment reaches the code host only when you submit the review.
- Advisory summaries, complexity, risk, and effort from enabled helpers
- Estimates are marked outdated when the pull request changes
Read the change in the order it makes sense.
File order puts the caller before the contract and the test three files from the behaviour it proves. Ask for a story and the same diff is ordered into stops — one idea at a time, gathering the hunks that belong together even when they sit in different files. Each stop says what changed and what to check; it never says the code is correct.
- Everything left off the path is listed, with the reason, and the counts match the file view
- The ordinary diff stays one click away, and your comments and drafts are untouched
- Stops you have opened are counted separately from files you marked reviewed
Ask about a file, a finding, or the whole change.
Ask your configured provider about a file, finding, or the pull request. An answer can become a staged comment; it still needs your review and submission.
- Scope the conversation to a file, a finding, or the whole pull request
- Runs on a CLI, a local model, or your gateway — same routing rules
- Turn any answer into a comment you still have to submit
Every prompt has an explicit context allowlist.
Each agent pairs a prompt with the pull-request context it may receive. You can inspect and change that selection before it runs.
You choose, per agent.
- Diff — the pull request's code diff
- PR details — title, description, changed files, open threads
- Linked ticket — a referenced Jira, Linear or Trello item
- Git history — recent commits on the changed files
- A named file — a specific path at the PR's latest commit
Agents produce findings or notes for the reviewer. They do not change code, commit, push, approve, merge, or resolve conversations.
Community agents show their full prompt and exact context before anything is saved, and an approved version keeps running until you review an update. The Security Reviewer, Performance Reviewer and Test Reviewer are good examples of how narrow a useful agent can be — browse the rest in the Agent Gallery.
Logs you own, on your machine.
Check AI runs and write actions from Settings → Logs on your machine.
- Settings → Logs → AI runs — metadata for every run, exportable as JSON. Storing the prompts themselves is an explicit opt-in.
- Settings → Logs → Write actions — every write PR Flow made for you, with a link to the result
The full picture is in the privacy policy and security overview, and the setup detail is in the AI features documentation.
Where the code goes.
Where does my diff actually go?
Can I run code review entirely offline?
What happens if I never turn AI on?
Can the AI approve or merge something?
Can a team force everyone onto one provider?
Where are API keys stored?
Keep AI advisory and under your control.
You still review the code and decide what to submit. Try PR Flow free for 14 days; a one-time licence keeps it after the trial.