Gemini Code Assist の無料 PR レビューが終わったあと — 代替の選び方The shutdown of the consumer-tier Gemini Code Assist GitHub bot is distinct…

For developers who relied on Google's free Gemini Code Assist bot to review pull requests on GitHub, a recent change has caused confusion — but the situation is more nuanced than "Gemini PR review is gone." The key distinction is that the shutdown affects only the consumer tier of Gemini Code Assist on GitHub, while a separate Google Cloud-backed version continues to operate under different terms.

Conflating these two offerings leads to one of two mistaken conclusions: either that all Gemini-based PR review has ended, or that the same free capability simply exists elsewhere. Neither is accurate. What has actually been discontinued is the Consumer, individual-facing version of Gemini Code Assist on GitHub. Meanwhile, Gemini Code Assist on GitHub delivered through Google Cloud remains available in Preview, but it requires a different setup path.

That setup difference matters. The Google Cloud route assumes you can provision and configure a Google Cloud Platform (GCP) project, which involves account setup, billing configuration, and the associated administrative overhead. This is a meaningful barrier for individual developers or small teams who previously benefited from the frictionless, zero-configuration nature of the consumer bot. The continuation of the Preview version, in other words, does not restore the same casual, install-and-forget experience that the free consumer tier provided.

Drawing this boundary first is the practical starting point for choosing a replacement. The decision appears to hinge on a few concrete questions. First, is the repository public or private? Second, are you able and willing to stand up a GCP project to access the Cloud-backed Preview? Third, are you already paying for or using adjacent tooling such as GitHub Copilot or Cursor? Each answer narrows the field of sensible options.

For teams already invested in GitHub Copilot, the platform has expanded its own automated code review features, which can review pull requests and leave inline suggestions directly within GitHub. Because these are integrated into the GitHub environment, they may be the lowest-friction substitute for those who already hold Copilot licenses. Similarly, Cursor — the AI-first code editor built on a fork of VS Code — has increasingly emphasized review and agentic workflows, and teams centered on that tool may prefer to keep their review loop within the same ecosystem rather than reintroduce a separate GitHub bot.

The choice is also shaped by repository visibility, because tooling access, pricing, and policy often differ between public open-source projects and private commercial code. Public repositories sometimes qualify for free or discounted tiers of review tooling, whereas private repositories typically fall under paid plans and stricter access controls. Anyone evaluating a replacement should confirm the current terms for their specific repository type rather than assuming parity across offerings.

It is worth situating this within the broader industry pattern. AI-assisted code review has become a crowded space, with vendors frequently launching free or preview-tier bots to attract users and later adjusting availability, pricing, or the required onboarding path as products mature. The retirement of a free consumer bot while a Cloud-backed, enterprise-oriented version persists is a familiar shape of this evolution, and it likely reflects a shift toward monetizable, account-anchored deployments rather than an abandonment of the underlying capability.

For readers deciding what to do next, the pragmatic sequence is to first confirm which offering they were actually using, then map their constraints — repo visibility, GCP feasibility, and existing subscriptions — onto the available paths. Those who can adopt the Google Cloud Preview retain a Gemini-based option, provided they accept the setup requirements. Those who cannot may find that a Copilot- or Cursor-based review flow better fits their workflow and billing situation.

The core takeaway is that "the free bot disappeared" and "Gemini PR review is finished" are not the same statement. Understanding that boundary prevents both premature panic and false reassurance, and it makes the subsequent choice among alternatives clearer and more deliberate.