Diff Digest v0.1.1 · macOS today · Linux & Windows next

The first diff viewer that spans every repo you're responsible for.

Diff Digest runs on your machine. It reads across organizations and repositories at once, and it ranks what changed by how much work it represents — not by what time it landed. We surveyed ten leading git viewers looking for another tool that does both. There isn't one.

Ten years of commit-crunching, packaged to run offline on a laptop.

diff-digest — browse — all organizations — last 90 days
Diff Digest's Browse tab, listing repositories ranked by how much substantive change each received over a selected time range.
Browse: every repo you have access to, ranked by volume of durable change. Drill from entity → organization → repo → file.

The vocabulary problem

Every diff tool ever built has two words for what happened to a line.

Added, or deleted. That's the whole vocabulary. So a file bathed in red might have been gutted — or it might have been renamed, reindented, or cut and pasted forty lines down. You can't tell without reading it, so you read it.

standard diff — is this deleted, or moved?
A heavily trafficked file rendered entirely in deletion red by a traditional diff viewer, giving no indication of whether the code was removed or relocated.
~25% of the lines a standard diff puts in front of a reviewer aren't durable change at all. Diff Digest classifies them and gets them out of the way.

What Diff Digest sees instead

Moved

Consolidating and refactoring are daily work. Cut-and-pasted lines and renamed files aren't deletions. They're relocations, and they're marked as such.

Updated

A line that keeps most of its value was tweaked, not replaced. Diff Digest highlights the changed fragment and carries the line's history forward.

Find & replaced

A project-wide rename is one decision, not two hundred. Review the decision once instead of scrolling past every instance of it.

Whitespace

Reindenting a block registers as a full delete in git. Unless you configure otherwise, Diff Digest treats it as the no-op it is.

Added and deleted still mean added and deleted. Six categories, not two.

Capability matrix

We went looking for a viewer that does this already.

We reviewed the ten most widely used downloadable git viewers of 2026 — their default landing views, their multi-repo features, and whether any of them distinguishes a consequential commit from a trivial one. Every one of them opens on a single repository's chronological commit graph. GitKraken Workspaces is the only real cross-repo layer on the market, and it aggregates branch status and open pull requests rather than change itself.

Supported Partial — see notes Not available
Capability Diff Digest GitKraken GitHub Desktop Sourcetree Tower Fork Sublime Merge SmartGit GitButler Lazygit
One activity view spanning many repositories not a repo list — a feed of what changed 1
Spans multiple organizations at once entity → organization → repo → file 1
Change ranked by impact, not chronology 2
Distinguishes moved code from added and deleted
Treats a tweaked line as an update carries the original line's history forward 3 3 3 3 3 3 3
Collapses a project-wide rename into one review
Suppresses whitespace-only noise by default not behind a toggle 4 4 4 4 4 4 4 4
Shows only what changed since your last review
Hover any line for the author's own explanation inside the diff, not a separate blame pane 5 5 5 5 5 5
Blame that follows a line through moves and renames
Runs locally, on your own machine
  1. GitKraken Workspaces group repositories across providers and support bulk fetch, clone and open, plus an aggregated pull request list. They surface branch status and PR state — not a combined feed of what changed inside those repos.
  2. GitKraken's Workspace pull request view shows a complexity indicator derived from raw lines, files and commit count. It is scoped to a pull request rather than a commit feed, and it does not appear in the commit graph.
  3. Most mature clients highlight changed words within a line. None of them reclassify the line as an update or carry its prior history forward, so the line still reads as one deletion plus one addition.
  4. Whitespace suppression exists in most clients as a setting a reviewer must find and enable, and it is generally not the default.
  5. Blame and annotate views exist widely, and GitLens surfaces line hovers inside VS Code. In every case the explanation lives outside the pull request diff you are actually reviewing.

Capabilities assessed against publicly documented behavior as of August 2026. Vendors ship quickly; corrections welcome.

What you get in the box

Built by people who review code every day, and resented every minute of it.

Why is this line here

The author already explained it. Diff Digest just puts the explanation where you'll see it.

Hover any line in a pull request and you get the commit message its author wrote when they made the change, along with what the line is worth. The more carefully your team commits, the more context reviewers inherit for free.

hover — line 675 — calculate-header-height.js
Hovering a changed line in Diff Digest reveals the authoring commit's message and the line's assessed value.

Rich blame

Standard blame stops at the last person who touched the file. This one keeps going.

The commit-crunching engine threads each line back through function moves, file renames, updates and find-replaces — so you can see how a line actually arrived at its current state, including how much of it originated with an AI assistant.

blame — following a line through its moves
Diff Digest's rich blame view, tracing a line's history back through file moves, function relocations and partial updates.

Resume where you left off

Come back to a long pull request and see only what moved while you were gone.

Diff Digest records which version of each file you reviewed, then assembles a diff that uses a different commit range per file. Files you already read show only their new changes; files you never opened show everything. One click at the top of any file expands it back to the full difference against main.

review — changes since your last session
Switching between changes since last review and the complete pull request changeset.

Triage before you start

Twenty minutes and forty changed files. Which four matter?

The file tree shows how much genuine change lives in each file before you open any of them, so a short review session lands on the code that needs a human rather than the code that got reindented.

file tree — weighted by review effort
Diff Digest's file tree, showing at a glance which files in a pull request carry the most substantive change.

Pricing

Every feature, for 75% of what GitKraken charges. Then you stop paying.

No seat tiers, no feature gates, no private-repo upcharge. One license, one payment, every capability in the matrix above.

$49.95 paid once · not per year
  • Cross-organization, cross-repository activity browsing
  • The full change lexicon: moved, updated, find-replaced, whitespace
  • Line-level hover explanations and history-following blame
  • Incremental review — only what changed since you last looked
  • Runs entirely on your machine, offline
  • Unlimited private repositories

What it needs

  • macOS 13 (Ventura) or later
  • Apple Silicon (M-series) Mac — Intel builds are not available yet
  • ~300 MB download; the app ships its own Ruby, PostgreSQL and git
  • Once installed, Diff Digest keeps itself up to date automatically

macOS today. Linux and Windows builds are next. Ten years of commit-crunching, now running on your laptop.