Built-in diff review
Review code changes in your terminal before you commit.
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 desktop window. No browser tab, no separate git GUI.
A full diff review, right in your workspace
Click any file to read its diff. Modified, added, untracked, and deleted: every change laid out before you commit, without leaving the terminal.
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.
Check Claude's edits before they're committed
A short lesson from the lpm series: Claude Code changes a page and a README, then you read every line, undo one file, and commit the rest without leaving lpm.
- 1
Open Review changes
When the agent is done, click the ⋯ menu above the terminal and choose Review changes, or press ⌘⇧R (Ctrl+Alt+Shift+R on Windows and Linux).
- 2
Read every change in one stack
Every changed file is shown as a diff, one after another, with the files listed on the right. Click one to see just that file, as a diff or as the whole file.
- 3
Undo what you don't want, commit the rest
Hover a file and click the undo arrow to put it back the way it was, then click Commit in the footer.
A code review surface built into your terminal
What changes when reviewing your own changes never asks you to leave the window.
Every change, one keystroke away
Press ⌘⇧R (Ctrl+Alt+Shift+R on Windows and Linux) and every uncommitted change stacks up in one scrolling view beside a tree of the changed files, each marked modified, added, deleted, renamed, or untracked. Unchanged lines fold away, and you can switch between split and unified.
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 commit it. The list refreshes on its own as the agent keeps writing.
Fix it in the diff
The right side of every diff is editable; save with ⌘S (Ctrl+S on Windows and Linux). If the agent rewrote the file while you were typing, lpm doesn't overwrite it and asks whether to keep yours or theirs.
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 leaving the window.
From review to commit in one flow
Open Commit, tick what belongs in it, and your AI agent writes the message. Commit it, or Commit and Push it in one go; Create PR drafts the GitHub title and description the same way.
Throw away what you don't want
Discard the changes to one file, a whole folder, or everything, with a confirmation first. Handy when an agent wandered into files it had no business touching.
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 where you left it.
Desktop app, keyboard-driven, zero Electron
lpm ships as a native desktop app for macOS, Windows and 64-bit x86 Linux. Its interface uses the system webview instead of bundling Electron or Chromium, and you can move through changed files from the keyboard.
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.
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 (Ctrl+Alt+Shift+R on Windows and Linux), walk the diff file by file, and catch the one place it dropped a null check. Fix the line right in the diff, save with ⌘S (Ctrl+S), and commit from the Commit dialog, all without leaving the agent’s window.
Read your own diff before every commit
You’ve been heads-down for an hour. Before you 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.
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.
What developers ask about reviewing changes in the terminal
How do I review changes in the terminal with lpm?
Press ⌘⇧R in a project (Ctrl+Alt+Shift+R on Windows and Linux). Every uncommitted change appears as one scrolling stack of diffs beside a tree of the changed files, each marked modified, added, deleted, renamed, or untracked, with added lines in green and removed lines in red. Switch between split and unified layouts, or open the Files tab's Changes view to step through files one at a time. The review sits in a pane 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, often yes. lpm gives you a file-by-file diff, a Commit dialog, and Create PR in the same workspace as your terminals, services, and AI agents, with no browser tab and no second app. It focuses on the read-and-commit loop: there is no branch graph, no hunk-by-hunk staging, and no review comments, so keep a git client or GitHub around for those.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 compared with the last commit, so you can read the full diff before you decide what to commit. The Commit dialog then commits exactly the files you tick, whole files at a time.Can lpm write the commit message for me?
Yes. In the Commit dialog, Generate with AI hands the selected files to whichever coding agent you use (Claude Code, Codex, Gemini CLI, or OpenCode) and it returns a conventional-commit message. No model runs on lpm's side; the agent uses your own sign-in, and you can add style instructions of your own.Can I review changes from my iPhone?
Yes, with the lpm Link iPhone app paired to your computer. It shows every changed file's diff with syntax highlighting, lets you mark files as viewed, and can commit the selected files or create a pull request, while the git work itself runs on your computer.Is the diff viewer part of the desktop app or a browser page?
The diff viewer is built into lpm's desktop app alongside your terminal panes. lpm uses the system webview for its interface instead of bundling Electron or Chromium, so the review stays in the same app window rather than opening a separate browser page.
Keep reading
Git terminal for Mac
Branch, rebase, and push right beside your running dev servers — all in one native window.
Best terminal for Claude Code and Codex
Live Claude Code and Codex status, alerts when one needs you, and their changes one keystroke away.
Git worktrees for AI agents
Give each agent its own checkout, then review each one's diff before you merge it.
Let agents drive lpm
Agents boot the stack, check the logs and hold until the port answers, so changes arrive tested.
Terminal with a project sidebar
See which project's agent finished, then open it and review what it wrote.
Review from your iPhone
Read diffs, mark files viewed, and commit from the lpm Link app while your computer does the work.
Read every diff before you commit.
Right where you already work.
Download lpm and open a project. Every change your agents make is one keystroke from a full diff, beside your running services. Runs on macOS 12 or later (Apple Silicon and Intel), with builds for Windows 11 (x64) and 64-bit x86 Linux.