# Rush vs Graphite

Graphite is a review workflow; Rush is an agent. They overlap only where Graphite's AI reviewer and Cursor's fix agents do Rush's job.

Facts checked 17 October 2026. Prices and limits move. Read the citations.

**The short answer.** Keep Graphite for stacking and the merge queue. Use Rush when the agent reviewing or fixing the pull request should be Claude Code, Codex or OpenCode, without a Cursor plan.

## The useful distinction

Graphite: a GitHub code review platform with stacked pull requests, a merge queue, AI reviews and Graphite Chat, with Cursor Cloud Agents on the pull request page. Cursor agreed to acquire it on 19 December 2025.

A review bot reads the diff and comments. An agent in a sandbox can also check out the branch, run the tests and push a fix. Both are useful; they are different jobs.

## Buyer questions

| Question | Rush | Graphite |
| --- | --- | --- |
| What runs | Claude Code, Codex or OpenCode, the vendors' own CLIs, or a saved agent built on one. | Graphite Agent for AI reviews; Cursor Cloud Agents for fixes from the pull request page. |
| Isolation | One E2B microVM per run with its own disk, memory, desktop and browser. It parks between turns and is removed on cancel or after 7 idle days. | SOC 2 Type II. The core app stores basic profile metadata; source code is fetched from GitHub. No self-host found; GHES on Enterprise. |
| Result and pull request | A run on a repository works on its own branch and opens the pull request; a run whose checks fail ends needs_review, not completed. Reports and files come back as artifacts. | GitHub only. One-click suggestions and fixes for failing checks in the pull request; Cursor Cloud Agents commit to the branch. |
| MCP | Rush is an MCP server at api.prix.dev/mcp with 18 tools. A run also takes MCP servers by connection or inline. | GT MCP (beta) in the gt CLI lets an agent create stacked pull requests: claude mcp add graphite gt mcp. |
| Team | Everyone in the org sees the same Projects and runs, with who started each. Automations start runs from GitHub events, schedules, webhooks and Linear. | Stacked pull requests, merge queue, review inbox and custom rules in plain language. |
| Starting price | Free 5 agent-hours / month; Pro $20; Team $200 | Hobby free with limited AI; Starter $20 / user / month and Team $40 / user / month, billed annually |
| Where it taps out | Three harnesses. Repositories through the GitHub App only. No self-host or customer VPC. A key runs 4 at once by default, up to 100. | GitHub only. Fixing with Cursor Cloud Agents needs a separate Cursor plan. Hobby AI limits are unpublished. The AI review docs do not say reviews run code. |

## When each side wins

### Rush wins when

- You want a reviewing agent and a fixing agent without a second editor subscription.
- The agent is Claude Code, Codex or OpenCode on your own model account.
- Review is one of many jobs started by the same API.

### Graphite wins when

- You want the whole review workflow: stacked pull requests, a merge queue and a review inbox, not only a bot.
- You want SOC 2 Type II with source code kept off the vendor's servers for the core app.
- Your team already pays for Cursor and wants Cloud Agents one click from the pull request.

## Where Rush sits

Rush does not replace stacked pull requests or a merge queue. It runs the agent: a review automation on pull_request.opened, or a run that fixes the failing check and pushes to the branch, on your own Claude or ChatGPT account.

## Skip Rush if

- Rush runs three agents: Claude Code, Codex and OpenCode. It does not host an agent you wrote yourself.
- Repositories come through the Rush GitHub App. A GitLab or Bitbucket repository cannot be a run's repository yet.
- There is no self-hosted or customer-VPC deployment, and we do not publish a compliance report today.
- Compute is metered. Free includes 5 agent-hours a month and Pro 40, each with a weekly ceiling.
- You review the pull request. Rush does not merge for you.

## Questions people actually ask

### Is Graphite owned by Cursor?

Cursor's blog of 19 December 2025, Graphite is joining Cursor, says Graphite entered a definitive agreement to be acquired by Cursor and will keep operating independently with the same team and product.

### Can I move from Graphite to Rush?

Graphite is a review workflow (stacks, merge queue, inbox) that Rush does not replace, so there is no migration. Rush can take over the AI review and the fix runs while Graphite stays.

### Does Rush need my own model account?

By default a run uses your own Claude or ChatGPT subscription or API key, and your provider bills the model calls. Rush meters the sandbox compute against your plan, and parked time is free.

## Keep reading

- [Graphite alternatives](https://getrush.ai/compare/graphite-alternatives.md)
- [CodeRabbit vs Graphite](https://getrush.ai/compare/coderabbit-vs-graphite.md)
- [Greptile vs Graphite](https://getrush.ai/compare/greptile-vs-graphite.md)

## Sources

1. Rush, "Rush product requirements", retrieved 2026-09-15. https://getrush.ai/cloud
2. Rush, "Rush pricing (live contract on getrush.ai)", retrieved 2026-09-15. https://getrush.ai/pricing
3. Rush, "Isolation, plainly", retrieved 2026-10-17. https://getrush.ai/docs/concepts/isolation
4. Rush, "Results and proof", retrieved 2026-10-17. https://getrush.ai/docs/concepts/results-and-proof
5. Rush, "Usage and billing", retrieved 2026-10-17. https://getrush.ai/docs/concepts/usage-and-billing
6. Rush, "Rush MCP server", retrieved 2026-10-17. https://getrush.ai/docs/concepts/mcp-server
7. Rush, "Automations", retrieved 2026-10-17. https://getrush.ai/docs/concepts/automations
8. Graphite, "Graphite Pricing", retrieved 2026-10-17. https://graphite.com/pricing
9. Graphite, "Graphite docs", retrieved 2026-10-17. https://graphite.com/docs
10. Graphite, "AI reviews", retrieved 2026-10-17. https://graphite.com/docs/ai-reviews
11. Graphite, "GT MCP", retrieved 2026-10-17. https://graphite.com/docs/gt-mcp
12. Graphite, "Privacy & security", retrieved 2026-10-17. https://graphite.com/docs/privacy-and-security
13. Graphite, "Graphite Chat / Agent feature page", retrieved 2026-10-17. https://graphite.com/features/agent
14. Graphite, "Introducing Cursor Cloud Agents in Graphite", published 2026-03-02. https://graphite.com/blog/cursor-cloud-agents
15. Cursor, "Graphite is joining Cursor", published 2025-12-19. https://cursor.com/blog/graphite
16. Graphite, "Graphite vs CodeRabbit", retrieved 2026-10-17. https://graphite.com/l/graphite-vs-coderabbit