# GitWarren

GitWarren is a local code-review tool for inspecting and commenting on the staged, unstaged, and untracked changes in an agent’s Git worktree before they are committed or pushed. It runs on the machine containing the repository and can be used through a desktop app, a browser, or an MCP server connected to coding agents.

- Findings24: <https://findings24.com/pt/tools/gitwarren>
- Site: <https://gitwarren.com>
- Preços: Freemium
- Categorias: Revisão de código com IA

## O que é GitWarren?

GitWarren is a code-review interface for work that has not yet become a commit. It reads a repository’s current worktree directly, combining staged, unstaged, and untracked files into a reviewable diff. This lets a developer inspect an agent’s output while it is still easy to change, rather than waiting for a push and pull request.

The review runs on the machine containing the repository. GitWarren can be used locally or reached on another machine over SSH, through a Tailscale tailnet, or from a Windows WSL distribution. It provides a desktop app and a browser-served version of the same UI, plus an MCP server that lets compatible coding agents participate in review discussions.

## O que GitWarren pode fazer?

### Worktree-level review

Combines staged, unstaged, and untracked changes into one diff, including files an agent created but has not added to Git.

### Review on the host machine

Reads Git and keeps review data on the computer where the repository lives instead of copying the repository to a hosted service.

### Desktop or browser interface

Use the desktop app on macOS, Windows, or Linux, or run \`gitwarren serve\` to open the same review UI in a browser, including on a headless machine.

### Remote machine access

Reach repositories on SSH hosts, Tailscale machines, or Windows WSL distributions. SSH hosts need Git; GitWarren supplies its own Node runtime for the remote installation.

### MCP agent participation

An MCP server over stdio gives compatible clients tools to open reviews, read discussions, reply in threads, comment on lines, and resolve comments.

### Attributed agent comments

Machine-written comments are marked as such, and separate MCP sessions receive distinct identities so concurrent agents can be told apart.

## Casos de uso

### Reviewing coding-agent output

Inspect an agent’s complete worktree, including untracked files, before its changes are committed or pushed.

### Working with a headless VPS

Run GitWarren on a server or build box with no screen and review the repository from another computer.

### Reviewing WSL repositories

Use a Windows WSL distribution as a review host while keeping Windows-native repositories supported as a separate workflow.

### Keeping agents in the discussion

Ask an MCP-connected agent to explain its diff or respond to a line comment in the existing review thread.

### Checking work across machines

Add SSH- or tailnet-accessible computers and open the review associated with the machine where the code is stored.

## Perguntas frequentes

### What does GitWarren review?

It reviews the current Git worktree, including staged, unstaged, and untracked files. The intended point in the workflow is before changes are committed or pushed.

### Does GitWarren copy my repository to a server?

The documented workflow keeps the repository, Git reads, SQLite review data, and attachments on the machine that owns the review. Remote access displays a view of that host rather than replicating the repository.

### Can it review code on another machine?

Yes. A machine can be added over SSH, through a Tailscale tailnet, or as a WSL distribution from Windows. SSH must already work without an interactive prompt, and the host needs Git.

### How can an agent connect to GitWarren?

GitWarren provides an MCP server over stdio. Its command-line setup creates a launcher for an MCP client, and the site documents setup paths for Claude Code, Codex, Cursor, VS Code, Kiro, Gemini CLI, and Goose.

### What platforms and interfaces are supported?

The desktop app supports macOS, Windows, and Linux. The command-line server serves the same UI to a browser, including on a headless machine; the documented \`npx\` route requires Node 22 or newer.

## Informações rápidas

- **Category**: Developer Tool
- **Primary workflow**: Pre-commit code review
- **Inputs reviewed**: Staged, unstaged, and untracked Git worktree changes
- **Interfaces**: Desktop app, browser-served UI, and MCP server
- **Remote access**: SSH, Tailscale tailnet, and Windows WSL
- **License**: GPL-3.0 open source