Devin Review 2.0, announced by Cognition on November 5, 2026, makes its AI pull request reviewer cheap enough to run on every PR. A typical review now costs $0.25 to $0.75, repeat runs review only new changes, and two new controls arrive: an Ultra effort level and custom reviewers in beta.
Last updated: November 9, 2026
Table of contents
- What is new in Devin Review 2.0
- Devin Review in August vs. November 2026
- How to set up automatic reviews
- Incremental reviews and cost controls
- Ultra effort and custom reviewers
- Provider support and limitations
- Frequently asked questions
- Sources
What is new in Devin Review 2.0
Devin Review is Cognition’s AI reviewer for pull requests. It groups related edits, explains them next to the diff, flags likely bugs and security issues, and offers a codebase-aware chat about the PR. With version 2.0, Cognition makes it the default review tool when you work with Devin. The Devin Review 2.0 announcement lists these changes:
- Lower cost. The cost of reviewing a PR fell 82% since August, which Cognition attributes to a better mix of models and harness optimizations.
- Incremental reviews by default. A second run on the same PR reviews only the parts that changed.
- Faster results. Median latency dropped to 94 seconds from 139 seconds.
- Automatic fixing with Devin. When Devin and Devin Review work together, Devin investigates each finding and decides whether to fix it, dismiss it or escalate it to you.
- Ultra effort level. A more thorough, more expensive review for sensitive code such as billing or security paths.
- Custom reviewers (beta). Named checks driven by your own instructions, with their own rules and findings.
Devin Review in August vs. November 2026
The figures below come from Cognition’s announcement. They are vendor-reported averages across its customers, not independent benchmarks.
| Metric | Since August 2026 | Devin Review 2.0 |
|---|---|---|
| Cost per PR review | Baseline | 82% lower; typical review $0.25 to $0.75 |
| Bugs found per PR | 1.22 on average | 1.32 on average |
| Median review latency | 139 seconds | 94 seconds |
| Repeat reviews on a PR | Full review | Incremental by default |
| Effort levels | One level | Normal (default) and Ultra |
| Custom checks | Not available | Custom reviewers in beta |
Cognition also says each bug that gets fixed costs about $2.25 on average, and that about 80% of PRs cost less than a dollar to review, including all pushes.
How to set up automatic reviews
You can try a single review without turning anything on. On GitHub, comment /devin review at the start of a comment on an open PR. The Devin Review documentation says the commenter needs write or admin access and a GitHub account linked to Devin. For ongoing coverage, set up rules:
- Open Settings, then Review, in the Devin web app (app.devin.ai/settings/review). Configuring rules requires the Manage Review permission.
- Add a rule and select a repository or another permitted scope.
- Choose the starting event: PR is created, which includes drafts, or PR is ready, which waits until the PR is marked ready.
- Choose the cadence: Only once or Every push. Every push requires the full automatic-review usage tier.
- Narrow the rule with conditions such as author, label, title, source or target branch, changed files or diff size, and add exclusions for PRs that should never be reviewed.
- Pick the review effort for the rule, or leave it on the account default.
- Under the posting settings, decide which findings go back to the PR as comments. Bugs and security findings post by default; investigate and informational flags do not.
Incremental reviews and cost controls
On a new push to a PR it already reviewed, Devin Review looks for bugs introduced or affected by the changes since the last run. It carries earlier findings forward and checks whether the new commits fixed them. If the new commits substantially change what the PR does, or the diff is too large for an incremental pass, it can review the whole PR again.
Reviews consume ACUs (Agent Compute Units) on enterprise plans, or included quota and on-demand credits on self-serve plans, as the Devin usage documentation explains. Three controls help keep spend predictable:
- Per-PR auto-review spend limit. Set it in Review settings. Leaving it empty uses a Cognition-managed default, not unlimited. When a PR reaches the limit, automatic reviews pause, but manual reviews still work.
- Review size indicator. Each PR shows a size pill, from XS (2.25 ACUs or less) to XL (more than 18 ACUs), so reviewers can see the cost of re-running reviews.
- Consumption dashboard. Enterprise admins can see review ACUs per user and per repository, including review counts and bugs caught.
If you are budgeting for the editor side as well, our guide to how much Windsurf costs covers the desktop plans.
Ultra effort and custom reviewers
Ultra. A Review manager chooses Normal or Ultra as the account default. Normal prioritizes price-performance. A practical pattern is to keep Normal as the default and add a rule that applies Ultra only to paths such as payments, authentication or database migrations.
Custom reviewers. These run inside Devin Review using your instructions. To create one, open Review settings, find Custom reviewers, select Add reviewer, and write plain-text instructions or point it at a repository or organization skill. Then choose a finding urgency (Severe, Moderate or Info) and add a rule so it actually runs. An enabled reviewer with no matching rule does nothing. Cognition says it uses custom reviewers internally for backend security practices, safe database migrations, performant SQL queries and accessible UI components.
Good instructions say what to flag and what to ignore. Devin Review also reads repository instruction files such as REVIEW.md, AGENTS.md and CLAUDE.md for conventions.
Provider support and limitations
- Providers. GitHub (including Enterprise Server and Enterprise Cloud) has full support. GitLab, Azure DevOps, Bitbucket Data Center and Bitbucket Cloud support analysis, chat and auto-review, but some workflow actions are partial or missing.
- GitHub write access. Comments, reviews and merge actions need the Devin GitHub App; PAT-based connections are read-only.
- Beta features. Custom reviewers, Autoapprover and review-context instructions are in beta, and availability varies by account.
For the rest of Cognition’s tooling, see our Devin Desktop 3.11 guide and our SWE-2 Flash guide. If your team reviews code from chat tools, compare the GitHub Copilot in Slack and Teams guide, and for a terminal-first agent see Codex CLI 0.167.
Frequently asked questions
\n
What is new in Devin Review 2.0?
\n
Cognition says the cost of a review per PR fell 82% since August, to about $0.25 to $0.75 for a typical review. Repeat reviews on the same PR are now incremental by default, median latency fell from 139 to 94 seconds, and the release adds the Ultra effort level and custom reviewers in beta.
\n
How much does Devin Review cost?
\n
Cognition’s announcement puts a typical review at $0.25 to $0.75 and says about 80% of PRs cost less than a dollar to review, including all pushes. Reviews draw from the same ACU pool or on-demand usage as other Devin work, and admins can set a per-PR auto-review spend limit.
\n
How do I run Devin Review on a GitHub pull request?
\n
Comment /devin review at the start of a comment on an open PR in a repository covered by your organization’s Devin GitHub App. You need write or admin access and a GitHub account linked to Devin. You can also paste a PR URL into app.devin.ai/review, or swap github.com for devinreview.com in a PR link.
\n
What is Devin Review Ultra?
\n
Ultra is an effort level for more thorough reviews at a higher cost. Normal, the default, prioritizes price-performance. A Review manager sets the account default, and each automatic review rule can use that default or override it with Normal or Ultra.
\n
Does Devin Review work with GitLab, Bitbucket or Azure DevOps?
\n
Yes, with differences. All listed providers support diffs, bug catching, codebase-aware chat and auto-review. The /devin review comment trigger is GitHub only, and merge, draft and auto-merge actions are partial or unavailable outside GitHub, according to the Devin documentation.
Sources
- Cognition: Devin Review 2.0 (November 5, 2026)
- Devin documentation: Devin Review
- Devin documentation: Usage and ACUs
Image: Devin Review 2.0 announcement cover from Cognition, used for editorial purposes. FreeAnswers is not affiliated with Cognition.