Complete Graphite Agent Review (2026)

Graphite Agent is the AI reviewer inside Graphite’s GitHub pull-request platform. It comments on bugs, suggests fixes, and can carry a conversation about a finding. The same product also sells stacked pull requests, a review inbox, automation, and a merge queue.

Graphite makes most sense when a GitHub team wants smaller pull requests and a better review workflow as well as AI feedback. If you only need a bot to spot bugs, compare its per-seat cost with the other AI code review tools before moving your team into another interface.

Graphite Agent at a Glance

Graphite Agent is available on paid plans and the free personal tier. It connects to GitHub.

Area	Current Position	Trial Question
Git platform	GitHub	Repos sync cleanly?
Review trigger	New pull requests	Useful on routine work?
Context	Whole codebase claim	Finds cross-file bugs?
Tuning	Rules and exclusions	Noise falls over time?
Workflow	Stacks and merge queue	Team wants both?
Paid model	Per seat	Seat rules understood?

What Does Graphite Offer Beyond AI Review?

Graphite combines AI review with tools for managing small, dependent pull requests. Its product includes a CLI and editor extension for stacks, a web inbox, merge controls, team reporting, and GitHub sync. Agent is part of that wider review system.

This matters to buyers because the Team price covers unlimited Agent use alongside the wider review platform. If a team already wants stacking and a merge queue, the AI reviewer is one part of a larger purchase. If it wants only automated comments, the wider workflow takes time to learn.

Graphite says Agent can create PR titles and descriptions, review code, chat about findings, propose fixes, and summarise continuous-integration results on eligible plans. Custom rules, file exclusions, automations, and acceptance metrics add a feedback loop around those comments.

Start with what slows your team down. Slow handoffs may call for the inbox and stack workflow, while missed bugs may mean you need better review rules, more context or another reviewer. Merge delays may call for queue rules.

The bundle only pays off when the team uses those features.

How Does Graphite Agent Review Code?

Graphite Agent analyses pull requests in repositories selected by an admin, leaves inline comments on potential problems and can suggest fixes. The review dashboard reports pull requests reviewed, issues found, and acceptance rates.

Graphite's current product page says Agent analyses the entire codebase, learns from team feedback, and focuses on bugs instead of style. These are vendor claims that need a repository-specific trial.

Agent works alongside the continuous integration pipeline. It may find logic and edge cases that tests miss, while tests provide repeatable proof. Keep required checks and human approvals in place because a conversational reviewer cannot guarantee full coverage.

How Do Stacked Pull Requests Change Code Review?

Stacked pull requests divide a larger change into smaller, dependent reviews. Developers can ask for review on the first slice while building the next. Graphite tracks the chain and helps move later branches as earlier ones merge.

Smaller diffs can help both people and AI because each pull request carries a tighter purpose. The reviewer sees fewer unrelated edits, comments attach to a clearer unit, and authors can fix one slice without reopening a large change.

Stacks also alter the team’s daily Git work. Developers need the Graphite CLI or editor flow, must understand parent-child branches, and have to recover when a middle pull request changes. A mixed team, where only some authors stack, can create more coordination work than it removes.

Graphite Agent can run without stacked pull requests. The setup page says selected repositories receive automatic review on new pull requests. Trial that basic loop first if the team has not agreed to alter how it divides work.

How Much Does Graphite Cost?

Graphite's billing table lists Hobby for personal work, Starter at $20 per seat each month billed annually, Team at $40 per seat each month billed annually, and custom Enterprise terms.

Plan	Price	Access	Buyer
Hobby	Free	Limited reviews and chat	Personal repositories
Starter	$20/seat/mo (annual)	Limited reviews and chat	Small teams
Team	$40/seat/mo (annual)	Unlimited and tunable	Growing teams
Enterprise	Custom	Unlimited and governed	Large organisations

The Team plan adds review customisation, suggested fixes, CI summaries, code-indexing controls, privacy controls, automation, and a basic merge queue. Enterprise adds items such as SAML or SSO, audit logs, access controls, GitHub Enterprise Server, and private uploads.

Check who counts as a paid seat. Its pricing FAQ says anyone who joins the workspace or has a pull request reviewed by Agent counts as a team member. Ask Graphite how that rule applies to bots, contractors, occasional authors, and archived accounts.

The 30-day Team trial allows unlimited invited contributors, according to the billing docs. Use it to build a full seat list and a monthly cost before the trial ends. A five-person Team workspace lists at $200 each month on annual billing, while a larger author pool may alter that figure.

How Do You Set Up Graphite AI Reviews?

To set up Graphite AI reviews, an admin connects the GitHub App, syncs the required repositories and enables them in AI review settings. Agent reviews new and updated pull requests that match the settings.

You can tune Graphite with comment exclusions and custom rules. Exclusions stop known unhelpful comments, while rules state a practice the reviewer should enforce. The customisation guide recommends narrow prompts with clear examples.

A workable exclusion might say: “Skip performance comments for files under /scripts because each script runs once during migration.” A workable rule might require a public API field to appear in the schema and contract test. Both examples define a clear scope and evidence.

Generated files can be marked with linguist-generated=true in .gitattributes. Graphite says those files collapse in review, do not count toward a too-large PR check, and are skipped by Agent. Test this with your generated paths before relying on it.

How Can You Judge Graphite’s Review Quality?

Judge Graphite’s review quality by the valid bugs it finds, the time spent dismissing incorrect comments and the bugs it misses. Its customisation dashboard provides supporting metrics for each rule and exclusion. Rules report issues found, PRs reviewed, accepted issues, acceptance rate, and votes. Exclusions report the issues checked and filtered out.

Acceptance rate is a starting point, not a quality score. A developer may accept a small edit because it is cheap, while ignoring a more serious finding that needs design work. Pair the number with severity, fix size, later test results, and bugs found after merge.

Review each custom rule after enough pull requests to expose a pattern. A rule with many findings and few accepted fixes may be vague, wrong for part of the repository, or better handled by a deterministic check. Narrow it, split its scope, or remove it.

Exclusion data can expose overly broad review tuning. If one exclusion filters a large share of candidate findings, sample those hidden cases. A broad instruction that cuts noise can also conceal a valid performance or security issue outside the reason it was written.

Keep a list of bugs found by people or tests alongside Graphite’s dashboard. Check a cross-file change and a dependent stack, then compare the findings with a dedicated reviewer. The AI reviewer evaluation guide explains how to keep that comparison fair.

How Does Graphite Handle Repository Access?

Graphite accesses selected repositories through its GitHub App; code-indexing and AI privacy controls are listed on Team and Enterprise. Enterprise adds access controls, SAML or SSO, audit-log export, GitHub Enterprise Server, private uploads, and contract options. Exact settings should be shown in the plan you intend to buy.

Repository indexing raises data questions. Ask what Graphite indexes, where that index is stored, how soon deleted repositories leave it, which model providers receive code, and whether chat or suggested fixes create extra stored data.

The GitHub App permission set needs a repository-by-repository check. Confirm who can sync a new repository, enable automatic reviews, edit rules, view organisation metrics, and export audit records. Start with the fewest permissions and repositories needed for the trial. Add access only when the work requires it.

How Does Graphite Connect to Cursor?

Graphite connects to Cursor Cloud Agents so developers can request code changes from the pull-request page. A developer signs in with a paid Cursor account, authorises the GitHub organisation and grants access to the repository. The agent can create a draft pull request or update the author's existing branch.

Graphite supports continuing a Cursor Cloud Agent conversation inside the pull-request page. This is a shipped workflow, rather than only an acquisition roadmap. The integration requires Cursor Pro or above; do not assume Graphite's included AI reviews also cover coding-agent usage.

Graphite Agent and Cursor Bugbot have separate product and pricing pages. A paid Cursor connection for coding tasks does not mean Bugbot is included in a Graphite subscription.

What Are Graphite’s Main Limitations?

Graphite’s main limitations are its GitHub focus, per-seat costs and the work of adopting its wider review workflow. Graphite’s current public setup relies on its GitHub App. Teams on GitLab, Bitbucket, or Azure DevOps need another review route unless Graphite publishes a new integration.

Per-seat billing can spread beyond the small group that administers Graphite. Anyone whose pull request Agent reviews may count as a member. Teams with many occasional authors should settle the roster rules before enabling every repository.

My Verdict

Graphite Agent has the clearest case when a GitHub team also wants Graphite’s stack, inbox, automation, or merge-queue workflow. In that setting, unlimited Team-plan review joins a platform the team has another reason to use.

Run Agent alone on ordinary pull requests before changing Git habits. Adopt the wider platform if it catches useful bugs and saves enough review time to justify the price per person. If you only need a review bot, compare those results and costs with a dedicated reviewer.

Frequently Asked Questions

Is Diamond now Graphite Agent?

Graphite renamed Diamond and combined it with Graphite Chat under the Graphite Agent name in October 2025. Older Diamond reviews may describe prices, limits or screens that no longer apply.

Can I use Graphite Agent without stacked PRs?

Graphite Agent can review ordinary GitHub pull requests without requiring stacked PRs. An admin enables AI reviews for selected repositories, so a team can try the reviewer before changing how developers organise their branches.