Skip to content
DocsReview changes

The app

Review changes

See what your agents changed, drawn on the map, accept or reject it, and bring their work home.

Changes to review

Changes to review, on the right, lists what changed: your working tree, each agent’s work, branches and merges. Choose one to see it drawn on the map, file by file, so you see where in the codebase a change landed before you read a line of it. In the Normal window, Ctrl+Shift+R opens it.

The Diffs part keeps every past change, each drawn on the map the same way.

Accept or reject an agent’s changes

In a file a Claude Code agent changed, accept or reject each change (a hunk) or the whole file, and undo the last one.

A Codex agent’s changes show on its page, but cannot be accepted or rejected there. Review them in Changes to review, or in a terminal.

Which agent wrote this names the agent behind a line of code.

Bring an agent’s work home

An agent that worked in a worktree of its own made its changes on that worktree’s branch. Land the agent’s work, in the agent’s menu, brings its worktree’s changes home.

From a terminal, gr worktree land lands any worktree: it merges the worktree’s branch into its base branch, pushes, removes the worktree and its branch, and brings the map up to date. --no-push keeps it on your computer, and --dry-run prints what it would do. On a conflict it decides nothing for you and prints the command that backs out.

Source control

Source Control lists what changed in the repository: the working tree first, then pull requests, branches, merges and commits. Click a row to see that change drawn on the map, file by file. It shows once you are signed in.

It only reads: commit and push from a terminal, or ask an agent to.

Tests

The Tests part shows how your CI runs relate to your code:

  • Runs shows, for each run, how much of the code a change needed tested against how much its tests reached.
  • Saved shows what Graphide’s test selection would have saved on your CI: hours, then dollars, then how many failing tests it would still have run. It needs GitHub connected; the part offers Connect GitHub.

Both need you signed in.

These docs describe Graphide 0.2.16, the latest release. Something wrong or missing? Tell us onDiscord or at hello@graphide.com.