Graphite
graphite.devGraphite helps developers stack code changes on top of each other.
Can an AI agent use Graphite? Yes, without signing up. Our agent got into Graphite on its own in 6 minutes and did 1 of its 8 core tasks.
From finding it to leaving
What an agent managed without a person, at each step.
- On its own
Find
Docs it can act on: llms.txt and an MCP server.
57 doc pages read
- On its own
Get in
Got in without signing up.
6 minutes
- Partly
Use
Did: use the same commands through the built-in MCP server; restack local branches after the main branch moves, once the main branch is pulled with plain git. Not done: open, sync or merge pull requests.
1 of 8 core tasks
- Not reached
Pay
Paying needs an account.
- On its own
Leave
Nothing to cancel, made nothing to delete.
Getting in
1 of 4 ways in worked without a person.
The way that worked
Runs locally, no account6 minutes
- An inboxNot needed
- A browserNot needed
- A personNot needed
- Agent on a serverAPI, MCP, CLIPartlyWithout an account (runs locally) it makes its first API call and does 1 of its 8 core tasks, then stops.
- Assistant in its own browserLike ChatGPT agentNoStops at sign-up: it's blocked there.
- Signed agentKnown to CloudflareYesThe sign-up page opens.
Every way in
| Way in | What happened | Why |
|---|---|---|
| Runs locally, no account | Worked | Part of the work done |
| Continue with GitHub | Not tried | Not part of this drive |
| CLI code login | Not tried | Not part of this drive |
| Added by an admin | Not tried | Needs a person's account |
What an agent can do with Graphite
1 of 8 core tasks done, and 6 of 19 others.
Core tasks
- done there
- tried, not done
- offered, not tried
| Task | Result | Through |
|---|---|---|
| Create a stacked branch/pull request | Done | MCP: done thereCLI: done there |
| Sync local stack with remote and restack on top of trunk | Partly | CLI: tried, not done |
| Submit a stack of PRs to GitHub | Blocked | CLI: tried, not done |
| Review a pull request (diff, comments, versions) | Blocked | Web app: offered, not tried |
| Get an AI code review on a pull request | Blocked | Web app: offered, not tried |
| Chat with an AI assistant about a PR and apply its edits | Blocked | Web app: offered, not tried |
| Merge a PR or stack through the merge queue | Blocked | CLI: tried, not done |
| Triage pull requests in a unified inbox | Blocked | Web app: offered, not tried |
Reliability
100of 100
Core tasks that worked on all 3 runs
Handles mistakes
88of 100
Clear errors, retries without duplicates, honest limits
Surface tested
75of 100
Documented routes, tools and commands run and checked
Docs accuracy
96of 100
Documented operations that behaved as the docs say
Docs completeness
50of 100
How fully the docs describe each operation
What it can't do, and why
- Open, sync or merge pull requests Needs a Graphite account, and sign-up is only through GitHub.
- Use reviews, AI review, chat and the inbox These live in the web app behind a GitHub sign-in.
- Get an API key There is no public API; the CLI token is copied from the web app after sign-in.
- Buy a plan Card checkout is in the signed-in app; no agent payment option.
6 of 19 other tasks done
- Reorganize a stack (move, fold, split, squash, reorder branches)Done
- Navigate a stack (checkout, up, down, top, bottom)Done
- Track or untrack an existing git branch with GraphiteDone
- Undo the most recent Graphite mutationDone
- Distribute staged changes across downstack branches (absorb)Done
- Freeze or unfreeze a branch to prevent accidental editsDone
- Fetch a teammate's stack locallyBlocked
- Customize AI review behavior with exclusions and custom rulesBlocked
- Create an automation rule to add reviewers, labels, comments or Slack notices on matching PRsBlocked
- View team engineering insights and metricsBlocked
- Create a pull request with a Cursor Cloud Agent from a promptBlocked
- Receive Slack notifications for PR activityBlocked
- Use the VS Code extension to create and manage stacked PRs visuallyBlocked
- Configure CI optimizations for stacked PRsBlocked
- Integrate with an external merge queueBlocked
- Manage organization members and permissionsBlocked
- Configure SAML SSOBlocked
- Read the organization audit logBlocked
- Change the subscription plan or seatsBlocked
Surface audit: 59 documented operations, 48 run, 42 passed, 2 not as documented, 8 blocked (sandbox or plan limits), 3 left out to stay safe.
How an agent connects
MCP, CLI and llms.txt found.
MCP server
All testedOfficial server. Local stdio via gt mcp, 2 tools, beta.
2 tools across its docs
API
None foundOpenAPI
None foundCLI
46 testedgt 1.8.6 (npm @withgraphite/graphite-cli), about 50 commands.
55 commands across its docs
SDK
None foundllms.txt
YesAgent payments
None foundThe checkout wasn't reached: Starter, $20 a year.
Docs
Some gapsCovers getting started and auth.
Errors only mentioned in passing.
Code examples on only some pages.
1 of 5 documented ways to do the core work worked when tried.
57 of 58 pages read
Tips for agent builders
- Install gt from npm (@withgraphite/graphite-cli; the linux-x64 binary package holds the real binary) and pass --no-interactive to every command
- Use gt create -m, gt modify, gt restack, gt absorb and gt fold for local stack work; they need no auth
- Pull trunk with git fetch and git merge --ff-only, then gt restack, when no Graphite token is set
- Add the MCP server with command gt, args [mcp]; check tool text for "ERROR:" since failures are not flagged isError
- gt split, gt reorder, gt config and gt demo are interactive only
How Graphite compares
In Source control
1st of 1 Source control product our agent got into on its own.
| Product | Level | Find to leave |
|---|---|---|
| L2 | Find: On its own, Get in: On its own, Use: Partly, Pay: Not reached, Leave: On its own. | |
| L1 | Find: Stopped, Get in: Stopped, Use: Not reached, Pay: Not reached, Leave: Not reached. | |
| L1 | Find: On its own, Get in: Stopped, Use: Not reached, Pay: Nothing to do, Leave: Not reached. | |
| L1 | Find: On its own, Get in: Stopped, Use: Not reached, Pay: Not reached, Leave: Not reached. | |
| L1 | Find: On its own, Get in: Stopped, Use: Not reached, Pay: Not reached, Leave: Not reached. |
Sorted by level, then work done, then time to the first call. How we rank
For the team behind Graphite
Our agent got through Use only in part, and didn't reach Pay. Prove Graphite is yours, then see where each issue is, read your safety findings and ask for a free drive after a fix. How to fix each one comes with the Audit.
6 things to fix for agents
Agent blockers: 3 foundAgent surfaces: 4 issues foundSafety review: no issues found
- FindClear
- Get inClear
- UsePartly
- PayNot reached
- LeaveClear
On our standard
16 criteria: against other source control products where we measured 5 or more, otherwise against every product we measured.
- Every way in works for an agentThe best result All 4 others (source control products) lower.
- Agents pick the right toolAhead of most 46 of 65 others (every product) lower, 19 the same.
- A tool list that fitsAhead of most 33 of 65 others (every product) lower, 32 the same.
- Sign-in for agents acting for a personLevel with most 64 of 119 others (every product) the same, 55 lower.
- Export before leavingBehind most 89 of 144 others (every product) higher, 55 the same.
- Prices an agent can readBehind most 81 of 105 others (every product) higher, 14 the same, 10 lower.
- Truthful annotationsBehind most 48 of 65 others (every product) higher, 17 the same.
- The best way in is built for agentsBehind most 3 of 4 others (source control products) higher, 1 the same.
All 16 criteria
- Descriptions that say when to use the toolIn the middle 20 of 65 others (every product) lower, 30 the same, 15 higher.
- Tool names that sort themselvesLevel with most 61 of 65 others (every product) the same, 4 lower.
- A path written for agentsLevel with most 71 of 141 others (every product) the same, 39 lower, 31 higher.
- WebMCP tools on the web appThe same as all 4 others (source control products).
- Typed, tight input schemasLevel with most 39 of 65 others (every product) the same, 10 lower, 16 higher.
- Docs an agent can navigateLevel with most 87 of 141 others (every product) the same, 10 lower, 44 higher.
- Spend an agent can see and capLevel with most 84 of 118 others (every product) the same, 34 higher.
- Pages fit one fetchLevel with most 87 of 141 others (every product) the same, 54 higher.
Where Graphite fits
- Category
- Wall
- Sign-up or key only in a browserour agent got in another way
Cited in 1 article
Found an error? Tell us on this page or read how corrections work.
Questions people ask about Graphite
- Can an AI agent sign up for Graphite on its own?
- Our agent got into Graphite without signing up. Its way in: Runs locally, no account, in 6 min.
- Does Graphite have an MCP server, and can an agent connect to it?
- Yes. Graphite has an official MCP server. The server runs on the agent's own machine and lists 2 tools. A new agent can get in on its own: in the drive of 28 Oct 2026, our agent got working access without signing up.
- How does an AI agent get a Graphite API key?
- In the drive of 28 Oct 2026, our agent needed no key. Not needed: a documented route works without an account.
- Can an AI agent delete its Graphite account?
- Not applicable: our agent used Graphite without an account, and it made nothing to delete.
Cite this page
The page as a reference, in plain text, APA and BibTeX.
Cite this
AgentDrives, “Graphite: AI agent test drive”, 28 October 2026, https://agentdrives.com/tools/graphite. CC BY 4.0.
AgentDrives. (2026, October 28). Graphite: AI agent test drive. https://agentdrives.com/tools/graphite
@misc{agentdrives_graphite_2026,
author = {{AgentDrives}},
title = {Graphite: AI agent test drive},
year = {2026},
month = oct,
url = {https://agentdrives.com/tools/graphite},
note = {Agent test drive, CC BY 4.0},
}Something wrong on this page?
Tell us what's wrong. We check it against the drive and correct the page, with the date.