Revue
Reads local Git repositories to present changes in a browser UI for review: uncommitted work, any commit's history, or a branch against its base, alongside the full file tree. Supports split/unified diffs with syntax highlighting, go-to-definition, before/after images and markdown previews, live refresh on edits/commits/branch switches, and lets an agent open its changes, scroll to the relevant lines, and leave notes on them.
✨ Highlights
🤖 Made for coding agents: over MCP, an agent opens its changes for you, points you at lines and leaves notes on them.
⚡ Live: the page updates as you edit, commit or switch branches.
🔀 Three modes: Changes (your uncommitted work), History (any commit) and Branch (a branch against its base, like a pull request).
🌳 The whole file tree with changes marked, for any local or remote branch, without checking it out.
🆚 Split or unified diffs with syntax highlighting and the changed part of each line marked.
🧭 Go to definition: Ctrl+click (⌘+click) a name to jump to where it's defined.
📷 Images and markdown: changed images before and after, side by side, and a sanitized markdown preview that draws Mermaid diagrams.
📁 Plain folders: point it at any folder to browse its files and docs.
🔒 Stays local: it listens on 127.0.0.1 only, and changes your files only when you check out a branch (security).
Related MCP server: Universal Change Review
📦 Install
Download, unpack, run. revue is a single binary that needs git and a browser from 2024 or later (Chrome or Edge 123, Firefox 121, Safari 17.5; it's tested in Chromium and Firefox), and no Rust, Node or other runtime.
Platform | Download | Notes |
🍎 macOS (Apple Silicon and Intel) | Signed and notarized by Apple | |
🐧 Linux x86_64 | Static, runs on any distribution | |
🐧 Linux ARM64 | Static, runs on any distribution | |
🪟 Windows x86_64 | Experimental |
curl -fsSLO https://github.com/jmsheas3/revue/releases/latest/download/revue-macos-universal.pkg
sudo installer -pkg revue-macos-universal.pkg -target /This installs revue in /usr/local/bin, as double-clicking the .pkg does. A newer .pkg upgrades it in place. To uninstall:
sudo rm /usr/local/bin/revue && sudo pkgutil --forget io.github.jmsheas3.revueThe .tar.gz holds the same signed binary, to put anywhere on your PATH without an installer.
curl -fsSL https://github.com/jmsheas3/revue/releases/latest/download/revue-linux-x86_64.tar.gz | tar -xz
sudo install revue-linux-x86_64/revue /usr/local/bin/On ARM64 (uname -m says aarch64), use revue-linux-arm64 in both lines. Without sudo, install -D revue-linux-x86_64/revue ~/.local/bin/revue puts it in your home folder instead; make sure ~/.local/bin is on your PATH.
Invoke-WebRequest https://github.com/jmsheas3/revue/releases/latest/download/revue-windows-x86_64.zip -OutFile revue-windows-x86_64.zip
Expand-Archive revue-windows-x86_64.zip -DestinationPath . -Force
.\revue-windows-x86_64\revue.exe --versionMove revue.exe to a folder on your PATH to run it as revue. To update, stop any running revue first: Windows can't replace a revue.exe that is running.
Every release lists each file's SHA-256 in SHA256SUMS:
curl -fsSLO https://github.com/jmsheas3/revue/releases/latest/download/SHA256SUMS
sha256sum -c SHA256SUMS --ignore-missing # Linux: checks the files you downloaded
shasum -a 256 revue-macos-universal.pkg # macOS: prints the hash to compare with SHA256SUMS(Get-FileHash revue-windows-x86_64.zip).Hash # Windows: compare with SHA256SUMS (case doesn't matter)🔄 Updating: download again and replace the binary. A revue that is still running shows a Server out of date badge until you restart it.
🦀 From source
With Rust 1.88 or later:
cargo install --locked --git https://github.com/jmsheas3/revueThat puts revue in ~/.cargo/bin, and cargo uninstall revue removes it. ⚠️ cargo install revue installs an unrelated crate that has the same name.
🚀 Quick start
revue # in a git repo: starts a server and opens your browser
revue ~/code/proj # point it at a repo (any folder inside one works)
revue ~/notes # a folder that isn't in a repo opens as a plain folderThe page opens on your uncommitted changes: every changed file's diff, one after another, next to the file tree.
Press | To |
| step to the next / previous changed file |
| go back to all of them |
| switch between Changes, History and Branch |
Ctrl+click (⌘+click) | go to a definition |
| list every shortcut |
revue prints the page's address and listens on port 4777, or on a free port if that one is taken; Ctrl+C stops it. See every option and shortcut, and plain folders for folders outside a repo.
🤖 Use it with coding agents
revue mcp is an MCP server, built into the same binary. With it, an agent can open its changes in your browser, scroll you to the lines it means and leave notes on them. For Claude Code:
claude mcp add -s user revue -- revue mcpUsing Antigravity CLI, Cursor CLI or GitHub Copilot CLI? Here's how to add it. Other MCP clients take the same command, usually as { "mcpServers": { "revue": { "command": "revue", "args": ["mcp"] } } }.
Then ask things like 💬 "show me the code changes", "show me the lines you just changed" or "leave notes in revue on anything I should double-check".
👉 Tools, arguments and how agents share servers
📚 Documentation
✨ Features: coding agents, live updates, modes, the file tree, diffs, go to definition, images, markdown
⌨️ Keyboard shortcuts: every key, in a repo and in a plain folder
📁 Plain folders: a document viewer for any folder
🤖 Coding agents (MCP): setup, tools and server lifetimes
⚙️ Command-line options: every flag and environment variable
🔒 Security: what revue writes, who can reach it, and how it treats repo content
🤝 Contributing: building, testing, pull requests and releases
🤝 Contributing
Bug reports and ideas are welcome as issues. Pull requests go into develop; CONTRIBUTING explains how to build, test and release. To report a vulnerability, please follow SECURITY.md instead of opening an issue.
📄 License
MIT; see LICENSE. The UI includes highlight.js (BSD-3-Clause), marked (MIT) and DOMPurify (Apache-2.0 or MPL-2.0), unmodified in public/vendor/; their license texts are in THIRD_PARTY_LICENSES. The binaries are also built from Rust crates under their own licenses (MIT, Apache-2.0 and a few others); each release lists them, with their license texts, in THIRD_PARTY_LICENSES_RUST.
Available Tools
10 toolsrevue_annotateA
Leave a note on a line or line range, shown inline in revue under those lines (in the diff and the file view), and show it to the user. Use it to explain a change, flag something to review, or ask a question about specific code. Notes belong to the current view (mode/ref/base/head) and are marked outdated if the lines change later.
Inputs: line (required), path (required), text (required), git, +11 more.
revue_annotationsB
List or clear notes left with revue_annotate. By default this acts on the notes of one view (mode/ref/base/head); all=true covers every view.
Inputs: id, all, git, ref, +6 more.
revue_changesA
List the files changed in a view of the repo (uncommitted work, a commit, or a branch vs its base), with status and added/deleted line counts. Returns text to you; to show changes to the user, use revue_open or revue_show.
Inputs: git, ref, base, head, +3 more.
revue_definitionsA
Find where an identifier (function, class, type, variable...) is defined, at the revision a view shows (in a plain folder, in its files). A fast git-grep heuristic, not a compiler: JS/TS, Python, Go, Rust, C-family and shell, with a loose fallback for other languages. The best match comes first, marked with * when it is a clear winner.
Inputs: name (required), git, ref, base, +6 more.
revue_diffA
Unified diff of one changed file, or of every changed file, in a view of the repo. Includes untracked files in the working tree view. Returns text to you; to show changes to the user, use revue_open or revue_show.
Inputs: git, ref, base, head, +5 more.
revue_logC
Recent commits on a branch (default: the checked-out one), or on all branches.
Inputs: all, git, repo, skip, +3 more.
revue_openA
Open revue, the browser-based git change viewer, on the overview of all changed files. Use this when the user asks to see or review code changes, rather than printing a diff. Starts a revue server for the repo if needed and reuses an open revue tab when there is one.
Inputs: git, ref, base, head, +4 more.
revue_showA
Show the user a file in revue, optionally scrolled to a line or line range. Use this to point at specific code: "look at server.js lines 120-140". With a line it defaults to the whole-file view; without one, to the diff. view "preview" shows a markdown file rendered (with its mermaid diagrams drawn), an SVG drawn as an image, or a mermaid file's diagram. In a plain folder (not a git repo) it is the file or its preview.
Inputs: path (required), git, ref, base, +9 more.
revue_statusA
List running revue servers (all repos, or one), with their port, lifetime, note storage and open tabs.
Inputs: git, repo.
revue_stopA
Stop the revue server for a repo, if this MCP server or an earlier one started it. Servers the user started by hand are left alone.
Inputs: git, repo.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 10 tools
Each tool has a mostly distinct role: text-returning inspection (changes, diff, definitions, log), browser presentation (open, show), annotation lifecycle, and server lifecycle. The only mild overlap is revue_show vs revue_open and revue_changes vs revue_diff, but their descriptions clearly distinguish showing code in the viewer from opening the overview and listing changed files from producing a diff.
All tools use the same revue_ prefix and snake_case suffixes, making the namespace predictable. The suffixes mix verbs and nouns (revue_open, revue_stop, revue_annotate vs revue_status, revue_diff, revue_log), but this is a minor deviation rather than an inconsistent scheme.
Ten tools is a well-scoped set for a git change viewer with annotations and server management. Every tool maps to a clear operation: presentation, inspection, annotation, or lifecycle.
The surface covers the core workflows: opening and showing code, listing changes, diffing, finding definitions, viewing logs, creating/listing/clearing annotations, and managing the revue server. Minor gaps exist around editing or deleting individual annotations, but clear-all support and the overall lifecycle are adequate for the domain.
Maintenance
Related MCP Connectors
AI-native git hosting — repos, PRs, issues, CI gates, and AI code review over MCP (60 tools).
Comment on AI-generated webpages; feedback flows back to your coding agent. Free, MIT, local-first.
Git collaboration for AI agents and people: tasks, hand-offs, reviews, teams, shared memory.
Team memory for AI coding agents and code reviews, reviewed by humans and served over MCP.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceA local MCP server that lets AI agents publish markdown/HTML to a browser viewer with session management, revision diffs, and live updates via a single tool call.2MIT
- AlicenseNot gradedqualityDmaintenanceA local, read-only Git change review tool that provides total workspace diffs, staged/unstaged views, file-level inspection, and task-scoped snapshots for MCP-compatible clients like Codex, Claude Code, and Cursor.MIT
- AlicenseNot gradedqualityDmaintenanceA local-first MCP server that provides read-only access to Git repository history, exposing commit metadata and optionally content patches via configurable policies, with optional AI-powered analysis while never modifying Git state.12 npmApache 2.0
- AlicenseAqualityBmaintenanceLocal code review for people and their coding agents: an agent opens a review of its changes and hands over a link, the person comments on lines, and the agent reads the threads, replies and resolves what it fixed. Reads the git worktree directly, uncommitted work included; nothing leaves the machine.17127GPL 3.0