See what your coding agent actually changed

difVi draws an AI-written change as a map, from where a request comes in down to the tables it writes, so you can review it fast and send fixes back to the agent.

Mac appBeta·One email when your build is ready

Works with Claude CodeCodexCursor

difVi flow map of the Acme Shop gift-card changeThe redeemGiftCard mutation flows through the redeemGiftCard.ts handler, GiftCardService.ts and giftCardRepository.ts. Its effects: a new gift_cards table and an UPDATE to orders, both risky writes shown in red; an HTTP call to payments.example.com in amber; and a gift-card.redeemed event. GiftCardService.ts breaks an AGENTS.md rule: fetch where AGENTS.md forbids it.

Code is written by agents now, reviewing became the bottleneck

Agents change dozens of files in minutes. Line-by-line diffs weren't made for that.

42%

of committed code is AI-generated, developers say

Sonar · State of Code · Jan 2026
+91%

PR review time on teams with high AI adoption

Faros AI · data to Jun 2025
+154%

bigger pull requests as teams adopt AI

Faros AI · data to Jun 2025

Let the code tell you a story

Start at an entry point and follow it to every table, API call and event it touches.

working tree redeemGiftCard › 4 effects 0/7 viewed
AGENTS.md
8## HTTP and logging
9- Use httpClient for outbound HTTP. Never call fetch directly.
10- No console.* in src/. Use the logger.

Understand why every line changed

One click writes a walkthrough of the change in the order data flows. Ask why about any file, or select lines and ask about those.

working tree Local model · Ollamaor OpenRouter

w a tour of the change, in flow order

Send fixes straight to the agent that wrote the code

Comment on a line, or message the agent about the whole change. It gets your note, and when it's fixed, the map updates.

GiftCardService.ts Service · newAgent · whole change
you → Codex
Codex
Tested checkout with a $20 card on a $50 order. The card pays $20, payments charges $30, and both writes land.
2 files changed
Message Codex…Send now
Claude Code · idle

Steps: you comment on a line; the comment is delivered to the agent session that wrote it, via hooks, for Claude Code, Codex or Cursor; the agent fixes the code; the issue clears and the map refreshes.

Keep track of every agent you have running

See which ones are working, which are waiting on you, and jump between them from the keyboard.

Grouped by what needs you

All your worktrees and agents in one list. Menu bar, notifications and a dock badge when one is waiting.

Keyboard-first, in flow order

] jumps to the next unviewed file, in flow order. A fix takes four keys.

Keep your code on your Mac

The map and rule checks always run locally. AI summaries can run on Ollama, LM Studio or your own model server.

File lines
PR summary

Questions

I review agent code all day. The traditional diff is not enough anymore, so we had to do something.
— Henry, CTO of difVi
Does my code leave my Mac?

Not with a local model. The map, rules and issues always run on your Mac, with no account. If you pick OpenRouter for AI summaries, what that summary reads goes there with your own key.

Does it explain why the agent made a change?

Yes, with the optional AI. One click writes a walkthrough of the change in flow order. Each file shows why it changed, quoting the agent, a commit or the PR where it can, and you can select any lines and ask why. It runs on your local model or OpenRouter.

Which agents?

Claude Code, Codex and Cursor. Your comments go back to the session that wrote the code.

What can it review?

Web apps, front end and back end. More stacks are coming.

Is difVi an AI code reviewer?

No. It shows you the change so you can review it, and sends your comments to the agent. Use it alongside any review bot.

Can I review a GitHub pull request?

Yes. diffviz review #123 opens any branch or PR, compared against its real base.

Pricing?

Not yet. Early access is through the waitlist.

Get early access

Available on

Mac appBeta·One email when your build is ready