Preview. These maps are our reading of public sources and haven't been checked with the projects' maintainers yet.
Graphite
Stacked pull requests on top of GitHub: a CLI and VS Code extension to create stacks, a review UI and PR inbox, a stack-aware merge queue, and AI review.
graphite.com/Acquired
Acquired by Cursor (Anysphere), announced 2025-12-19 (TechCrunch, SiliconANGLE); graphite.com still sells Graphite and shows 'Cursor Cloud Agents are now in Graphite'. CLI @withgraphite/graphite-cli 1.8.6 last published 2026-05-05 (npm). (checked 2026-10-25)
In Version control beyond git
Where it stands apart
- How is the main thing licensed? proprietary or closed source (11% of 19 others)
- Can it run entirely on your own device or infrastructure, without the maker's servers? partly (some features need the maker's servers) (11% of 19 others)
- Do you need an account to use it? account required (22% of 18 others)
- Which shared standard or format does it mainly build on? GitHub pull requests (via the GitHub API) (0% of 20 others)
- Is it designed with AI coding agents in mind? it adds AI features, but is not designed around agents (5% of 20 others)
- Are stacked changes (a chain of dependent changes reviewed separately) a first-class workflow? yes, the workflow is built around stacks (20% of 15 others)
What it shares with most of the community
- Is it actively maintained? active (90% of 20 others)
- Who is it for? developers (90% of 20 others)
- How does it relate to git repositories? built on git: reads and writes git repositories directly (53% of 19 others)
- Can you commit, branch, and read history with no network connection? yes (94% of 17 others)
- What is the basic unit of history? (pick the most specific that applies) snapshots (commits) with no identity that survives a rewrite (74% of 19 others)
- How are merge conflicts mainly handled? must be resolved before the merge or commit completes (65% of 17 others)
- What size of project is it designed for? ordinary source repositories (74% of 19 others)
Nearest neighbors
- Cursor Origin 80% of 15 shared answers match
- zz 75% of 16 shared answers match
- Gitea 65% of 17 shared answers match
Every answer
| Question | Answer | Source |
|---|---|---|
| Is it actively maintained? | active Shipping, but now part of Cursor, which launched its own forge (Origin) in 2026. | source 2026-10-25 |
| How is the main thing licensed? | stands apart proprietary or closed source Proprietary; the CLI source repo (withgraphite/graphite-cli) is no longer public (GitHub API 404). | source 2026-10-25 |
| How is it mainly sustained? | company with a paid product, tier, or ads Paid SaaS; now owned by Cursor. | source 2026-10-25 |
| Can it run entirely on your own device or infrastructure, without the maker's servers? | stands apart partly (some features need the maker's servers) CLI runs locally on a git repo; review, merge queue, and AI review are hosted and require GitHub. | source 2026-10-25 |
| Do you need an account to use it? | stands apart account required CLI must be authenticated with a Graphite account via GitHub sign-in. | source 2026-10-26 |
| Who is it for? | developers | source 2026-10-25 |
| Which shared standard or format does it mainly build on? | stands apart GitHub pull requests (via the GitHub API) Stacked PRs on top of GitHub; GitHub is the system of record. | source 2026-10-26 |
| How does it relate to git repositories? | built on git: reads and writes git repositories directly | source 2026-10-25 |
| Where does the authoritative copy of a project live? | one central server per project (hosted or self-hosted) GitHub is the system of record. | source 2026-10-25 |
| Can you commit, branch, and read history with no network connection? | yes | source 2026-10-25 |
| Is it designed with AI coding agents in mind? | stands apart it adds AI features, but is not designed around agents AI review, Graphite Chat, and an 'Agents' section; the core product predates agents. | source 2026-10-25 |
| Which layer of the stack does it mainly replace? | the forge layer (hosting, review, or merging) Replaces GitHub's PR and review workflow, plus a CLI for local stacks; does not host repos. | source 2026-10-25 |
| What is the basic unit of history? (pick the most specific that applies) | snapshots (commits) with no identity that survives a rewrite | source 2026-10-25 |
| Are stacked changes (a chain of dependent changes reviewed separately) a first-class workflow? | stands apart yes, the workflow is built around stacks | source 2026-10-25 |
| How are merge conflicts mainly handled? | must be resolved before the merge or commit completes | source 2026-10-25 |
| What size of project is it designed for? | ordinary source repositories | source 2026-10-25 |
| Is code review part of the product? | yes, it has its own review interface Own review UI over GitHub pull requests. | source 2026-10-25 |
Sources
This page was derived from:
- Package registry · www.npmjs.com/package/@withgraphite/graphite-cli · read 2026-10-25
- Web page · graphite.com/ · read 2026-10-25
Are you a maintainer? Claiming and correcting projects is coming soon.