Gemini Code Assist code review alternatives and migration

• Code review
• Tools compared

Google shut down the consumer Gemini Code Assist app for GitHub on 17 July 2026, and stopped selling new Gemini Code Assist Standard and Enterprise subscriptions on 9 October 2026. If it was your free pull request reviewer, it has stopped reviewing. Pick a replacement by Git host, budget and whether it can block a merge, then work through the migration checklist below.

Disclosure: I build AI CodeOps, one of the five alternatives below. Facts about every product link to its own pages, checked on 24 October 2026, and each gets a fair "choose it if".

What changed and when

These dates come from Google's deprecations page (last updated 9 October 2026), its consumer code review sunset page and its Standard and Enterprise sunset page, all checked on 24 October 2026.

Two things to read carefully. First, Google says the enterprise version of Gemini Code Assist on GitHub "is not affected by these changes"; only the consumer app is gone. Second, existing Standard and Enterprise subscriptions keep working until the contract ends. Google's sunset page points those customers to Antigravity, which is included in Gemini Enterprise editions.

So if you installed the free app on a personal account or an organization, your reviews have already stopped. If you pay for Standard or Enterprise, you have until the renewal dates, but you can't add new subscriptions.

What you lose

The consumer app did a few specific things, and it's worth listing them so the replacement covers each one:

• An automatic review when a pull request opens, with the app added as a reviewer and each comment tagged Critical, High, Medium or Low.
• An optional pull request summary.
• Comment commands, such as /gemini review and /gemini summary.
• Repository settings in a .gemini/ folder: config.yaml (for example code_review.comment_severity_threshold and ignore_patterns) and a styleguide.md (customize).

Those files are still in your repositories. Nothing reads them now. The style guide in particular is often the most useful thing your team wrote for a reviewer, so carry it over rather than lose it.

Choosing a replacement

Four questions narrow the field quickly:

1. Git host. Gemini's app was GitHub-only, so most teams leaving it are on GitHub. If some of your code lives elsewhere, this is a chance to pick one reviewer for every host.
2. Budget. Several reviewers moved to usage-based billing in 2026. With five pushes per pull request, a tool that reviews every push runs five times as many reviews as one that reviews once (pricing compared).
3. A free or open-source plan. If you lost a free reviewer on public repositories, check which tools review public or open-source repositories for free.
4. Merge blocking. Gemini's reviews were comments. If you want a review that can stop a merge, you need a tool with a check that can fail, and a required status check on the branch.

Five alternatives in brief

The full comparison of 13 AI code review tools has every fact and price. These five cover most teams leaving Gemini.

GitHub Copilot code review. A reviewer you add like a colleague, or request automatically on every pull request with a ruleset (automatic review). It bills AI credits plus Actions minutes, and isn't on Copilot Free (code review). Choose it if you're on GitHub and already pay for Copilot.

CodeRabbit. The closest match to Gemini's comment-style review, on more hosts: GitHub, GitLab, Bitbucket and Azure DevOps. Public repositories get Team features free; paid plans start at $24 per developer a month on annual billing (pricing). Choose it if you want a bot on every pull request and maybe more than one Git host.

Sourcery. Reviews every pull request on GitHub and GitLab, and a blocking security comment fails its "Sourcery review" check (status checks). Free for public repositories, Pro from $12 per developer a month on annual billing (pricing). Choose it if you want a low per-seat price and a check you can require.

Cursor Bugbot. Reviews pull requests on GitHub, GitLab, Bitbucket and Azure DevOps, and can fail a required check on unresolved issues once you turn that on (docs). It's usage-based, at an average of about $1.00 to $1.50 a run (Cursor blog). Choose it if your team already uses Cursor.

AI CodeOps (ours). Not a drop-in replacement, and I'd rather say so up front: it doesn't review pull requests your team opens. AI agents write a change, run your tests, review the diff and hold it at a release gate until a person approves it. Then it opens the pull request on GitHub, GitLab, Bitbucket, Gitea or Forgejo. It's free during the open beta. Choose it if you want AI to write and gate routine changes, and keep one of the reviewers above for the code people write. The GitHub integration page and the GitHub setup guide cover the connection, and AI CodeOps vs Gemini Code Assist is the side-by-side.

If you're still mapping the options, what AI code review is covers what any of them can and can't catch.

The migration checklist

Copy this into an issue and tick it off per repository or organization.

GitHub's guide to reviewing and modifying installed GitHub Apps has the uninstall steps in full.

For step 3, the GitHub CLI shows what a branch requires. Replace OWNER/REPO and main with yours:

# Rules that apply to the branch, from rulesets (look for required_status_checks and pull_request)
gh api repos/OWNER/REPO/rules/branches/main

# Required status checks from classic branch protection (404 if the branch has none)
gh api repos/OWNER/REPO/branches/main/protection/required_status_checks

# Leftover Gemini settings in this repository
git ls-files .gemini

For step 5, here is where each reviewer reads repository instructions:

For Copilot, the style guide can move as it is:

mkdir -p .github
git mv .gemini/styleguide.md .github/copilot-instructions.md
git rm -r .gemini
git commit -m "Move review style guide from Gemini to Copilot"

Settings don't map one to one. Gemini's comment_severity_threshold and ignore_patterns have no shared format across tools, so write the intent into the new tool's instructions or settings ("ignore generated files under dist/", "only comment on medium severity and above").

Key takeaways

• The consumer Gemini Code Assist GitHub app stopped reviewing on 17 July 2026; the enterprise version is not affected, per Google.
• New Standard and Enterprise subscriptions ended on 9 October 2026; renewals end on 31 January 2027 (annual) and 31 December 2027 (monthly).
• Copilot code review and CodeRabbit are the closest like-for-like replacements on GitHub; Sourcery and Bugbot add a check you can require.
• Don't lose your .gemini/styleguide.md: move it into the new reviewer's instruction file, then delete the folder.
• Check your branch rules after uninstalling, so nothing required still points at an app that no longer runs.