klarluft/gitwarren-app

**Code review for your own git repositories, on your own machines.** Your
machines, your agents, no one else's server — and no account.
Built for the moment a coding agent — Claude Code, Codex, or anything else that
edits files on your disk — has just finished, and its work is sitting in your
worktree uncommitted. Read that diff here, on your own machine, before it
becomes a commit.
**gitwarren.com** has downloads for macOS, Windows and
Linux.
---
What it does
Tell GitWarren which local git repositories you care about, then open **reviews**
against them — a review is a comparison of two refs, presented the way a pull
request is, with *conversation*, *commits* and *files changed* tabs, and a
*browse files* tab for the code the change did not touch.
- **Review work before it is a commit.** If the branch you are reviewing is
checked out in a worktree, GitWarren finds that worktree — wherever it is — and
folds its staged, unstaged and untracked changes into the diff. That is exactly
when review is most useful, and it is the part that makes this worth having.
- **Prose as well as code.** Diffs read unified or side by side, with the
changed words picked out of a changed line. A Markdown file can be read
rendered, with its edits marked like tracked changes, and commented on
paragraph by paragraph.
- **Nothing is cached.** Every branch name, commit and diff on screen is read
from git at the moment it is shown.
- **Nothing leaves your machine.** Reviews live in one SQLite file in your
application-data directory. No account, no telemetry; the desktop app's one
outbound request is the update check.
- **Agents are first-class.** Local AI agents get the same capabilities through
an MCP server over stdio — they open reviews, read your comments, reply in a
thread and resolve what they fixed.
- **Desktop app or browser.** It runs as an Electron app on macOS, Windows and
Linux, or as a command that serves the same review UI into a browser tab. Same
renderer either way; the shell is the only thing that differs.
- **Your other machines too.** A machine with no screen at all — a VPS, a WSL
distro, a box an agent works on — runs the headless half and is reviewed from
somewhere else, over SSH, over wsl.exe, or over your own tailnet, and its
repositories are listed on the same home screen as this machine's. Reviews
live on the machine the code is on and stay there; nothing is replicated or
relayed anywhere but the computers you already own.
Comments go on the line, the way a pull request does them. The agent that
wrote the code answers in the same thread, while you are still reading the
diff:
---
Install
The desktop app
Download it from **gitwarren.com**, or on macOS:
The command line
Serves the same review UI in a browser instead of an Electron window — for a
machine that will not have the app on it, or one with no screen at all:
Then gitwarren serve --open. See
The gitwarren command line.
Into a coding agent
If you arrive from a coding agent, start here instead. The plugin brings the MCP
server and a note that teaches the agent when to open a review and how to answer
your comments:
Cursor, Codex, VS Code and Kiro read the same repository from their plugin
screens. See Installing it as a plugin.
---
Documentation
| Guide | What is in it |
| --- | --- |
| Reviews | What a review is, how uncommitted work is found, reading and navigating a large diff, side by side and wrapped lines, Markdown previews, browsing and searching the repository, marking files reviewed, opening a file in your editor, keyboard shortcuts |