Review changes in the terminal

See every change before you commit — without leaving your terminal.

lpm opens a full, file-by-file diff review right beside your running services and AI agents. Read what changed, catch what shouldn’t ship, and commit with confidence — in one native macOS window. No browser tab, no separate git GUI.

Download for macOS
Signed & notarized by Apple
Try it

A full diff review, right in your workspace

Click any file to read its diff. Modified, added, and deleted — every change laid out before you commit, without leaving the terminal.

saas-app · Review changes
Changes4 filesfeat/billing
Msrc/lib/billing.ts
@@ -14,9 +14,12 @@ export async function createSubscription(
1414 const customer = await stripe.customers.create({ email });
15- const price = PRICES[plan];
15+ const price = PRICES[plan] ?? PRICES.starter;
16+ if (!price) throw new Error(`Unknown plan: ${plan}`);
1617 return stripe.subscriptions.create({
1718 customer: customer.id,
19+ trial_period_days: 14,
1820 items: [{ price }],
1921 });
Reviewing before commit — no browser tab
The review context tax

Reviewing your changes shouldn't mean leaving your workspace

Every commit is a decision. Making it well means seeing the diff next to the tests, the logs, and the agent that wrote it — not in a window three apps away.

You leave your terminal just to read a diff

Your code and your running services are in the terminal. But to actually see what changed, you open a browser tab, a desktop git client, or your editor's source-control panel. The review happens everywhere except where the work does.

AI agents write more than you can read

Claude Code or Codex just touched twelve files. Approving blindly is how bugs ship; scrolling a cramped terminal diff is painful. You need a real review surface — right where the agent is working, not in a separate app.

Losing the diff means losing the context

Switch to a diff tool and you lose sight of the failing test, the streaming logs, the branch you're on. By the time you're back, you've forgotten which change you were checking and why it mattered.

Review where you work

A code review surface built into your terminal

Six things that change how reviewing your own changes feels when the diff never asks you to leave.

File-by-file diff, one keystroke away

Open a review pane with ⌘⇧R and every changed file is listed with an M / A / D status. Click a file to read its diff — added lines in green, removed in red, right there in the window you already work in.

Review AI-agent changes on the spot

When Claude Code or Codex edits your files, open the diff in the same workspace and see exactly what the agent did before you accept it. No blind approvals, no context-switch to a separate tool.

The diff sits beside everything else

Your review pane lives next to the failing test, the streaming service logs, and the agent terminal. Spot a regression in the diff and re-run the test in the pane beside it — without ever leaving the window.

Per-project, per-branch — always in context

Each project keeps its own workspace, so the changes you're reviewing are always for the branch and repo in front of you. Switch projects and come back — your review is exactly where you left it.

From review to commit in one flow

Read the diff, catch the stray console.log, fix it in the editor pane, and commit — a single, uninterrupted loop. The review is the last gate before your code ships, and it's built into the terminal.

Native, keyboard-driven, zero Electron

It's a real macOS app on Apple Silicon, not a web view. Navigate files with the arrow keys, scroll long diffs smoothly, and keep your hands where they already are — on the keyboard.

In practice

When reviewing changes in the terminal actually pays off

Three moments where jumping to a separate diff tool costs real time — and how lpm keeps the review right where the work is.

1

Vet what your AI agent changed before you accept it

Claude Code just refactored your billing module across eight files. Open the review pane with ⌘⇧R, walk the diff file by file, and catch the one place it dropped a null check. Fix it in the editor pane beside the diff, then commit — all without leaving the agent’s window.

2

Read your own diff before every commit

You’ve been heads-down for an hour. Before you git commit, open the review pane and actually read what you’re about to ship. The stray console.log, the commented-out block, the file you didn’t mean to touch — you see them here, not in code review tomorrow.

3

Catch a regression while the test is still on screen

A test just went red in one pane. Open the diff in another, scan what changed, and spot the off-by-one immediately — the failing output and the offending line are on screen at the same time. Re-run the test in the pane next door and watch it go green.

FAQ

What developers ask about reviewing changes in the terminal

  • How do I review changes in the terminal with lpm?
    Open a review pane in your project — a diff view lists every changed file with a Modified, Added, or Deleted marker. Click a file to read its diff inline, with added lines highlighted green and removed lines red, and navigate between files with the arrow keys. The review sits in a pane right beside your running services and terminals, so you never leave the window to see what changed.
  • Does lpm replace a git GUI like GitKraken or the GitHub diff view?
    For reviewing your own changes before you commit, yes. lpm gives you a fast file-by-file diff built into the same workspace as your terminals, services, and AI agents — no browser tab and no second app. It focuses on the read-and-commit loop rather than a full visual branch graph, so if you rely on click-to-cherry-pick GUI features you can still run a git client alongside it, but most developers find the built-in review is all they reach for.
  • Can I review the changes an AI coding agent made?
    That's one of the main reasons the review pane exists. When Claude Code or Codex edits files in an lpm terminal, open the diff in a pane right beside the agent and read exactly what it changed before you accept anything. You review the agent's work in the same window it's working in, instead of approving edits blindly or switching to a separate diff tool.
  • Do I need to stage or commit my changes first to review them?
    No. The review shows your working-tree changes — modified, newly added, and deleted files — so you can read the full diff before you decide what to stage or commit. It's the last gate before code leaves your machine, not something that only works after the fact.
  • Is the diff viewer a real native app or a web view?
    lpm is a native macOS desktop app built for Apple Silicon — no Electron and no bundled browser. The diff renders natively, scrolls smoothly on large files, and responds to keyboard navigation instantly, in the same window as your real terminal panes running your actual shell and dev servers.

Read every diff before you commit.Right where you already work.

Download a native macOS binary, drag to Applications, open your first project. lpm puts a full diff review one keystroke away — beside your running services and the AI agents editing your code. Works on every Intel and Apple Silicon Mac running macOS 12 or later.

Download for macOS
Signed & notarized by Apple