Review commit history and diffs on your computer from your phone

A practical workflow to review recent commits, open diffs, and answer “what changed?” from your phone, without needing remote desktop.

Based on
CLI
0.2.17
Preview ref
a2c45c8

A repeating “away from the desk” question:

What changed?

Not “what’s the perfect architecture?”

Not “what should be refactored next?”

Just: what changed, where, and can it be trusted.

This comes up when:

  • a teammate pings you about a regression
  • CI fails on a branch you haven’t looked at in days
  • you’re in the middle of a release
  • you’re reviewing your own changes from earlier

If the only way to answer is “remote desktop into the computer”, it usually gets postponed.

This guide covers a workflow that makes “review recent commits” possible from a phone.

Common approaches and their trade-offs

  • SSH: great for quick commands, but not great for visual diff review on a phone.
  • Remote desktop: works, but heavy and distracting.
  • Git hosting apps: great when the change is already in a PR. But sometimes you want to review a repo on your computer regardless of where it’s hosted (or before it’s pushed).

A workflow that works

This workflow uses a remote UI over the computer that owns the repo.

Happier is one option that supports that approach.

Each Happier session is attached to a repo folder on your computer. On a phone, the session's Git tab lets you:

  • browse commit history
  • open a commit and review its diff

Reading history and diffs works without turning on the experimental Git write actions.

Trade-off: your computer still has to be online.

If you’re new to Happier (what it is, and where to get it)

If you haven’t seen Happier before: it’s an open-source companion app (mobile/web/desktop) that lets you keep workflows on a computer you trust, then manage them from your phone.

Get set up:

Step-by-step: review commit history from your phone

1) Open a session in the repo folder

Open a session that runs in the repo, or start one with the repo folder as its working directory.

2) Open the Git tab's history

Inside the session:

  1. Open the Git tab.
  2. Open the commit history.

You’ll see:

  • Recent commits
  • a Load more commits action

3) Open a commit and review the diff

A simple phone review loop:

  1. open the most recent commit
  2. skim the commit message (intent)
  3. open the highest-risk file first
  4. decide: “looks good” vs “needs follow-up”

If you need “why did this happen?”, you can jump from history into:

  • Changed files for the current working tree

4) Use Files when you need context

History tells you what changed.

Sometimes you also need “what is this file?” context.

That’s when to open:

  • Files

Search, open the file, read it, and go back.

5) Make a follow-up decision

Most review workflows fail because they don’t end with an action.

Useful actions from a phone:

  • leave a review comment
  • ask for a one-paragraph rationale for a change
  • queue a small fix
  • or decide “this is fine” and move on

Terminal (optional)

Sessions can show a Terminal tab when the embedded terminal is available. It's experimental per the feature matrix.

Use it for one-off commands (git show, git grep, etc.), but keep the default workflow UI-first.

FAQ

Why would I use History instead of just looking at Changed files?

Changed files answers: “what is currently dirty in this working tree?”

History answers: “what happened over time?”

Both are useful; they answer different questions.

How far back can I go?

Use Load more commits.

Do merge commits show diffs?

In raw Git, merge commits often don’t show diffs unless you ask for a specific merge diff format.

If you’re reviewing merges, be extra deliberate about what you want to inspect (first-parent view vs combined diffs). (Source: https://git-scm.com/docs/git-log)

Can I review commit history without pushing to GitHub?

Yes.

That’s one of the core benefits of a session-based workflow: you can review what’s on your computer, not only what’s already pushed.

What’s the biggest failure mode?

The host computer goes offline.

If you can’t reliably keep the repo machine online, no phone workflow will feel stable.

How do I answer “what changed between these two points” from my phone?

Two practical approaches:

  1. Open the two commits in History and review their diffs one at a time.
  2. If you need a true “compare A…B” diff, use the Terminal for a one-off git diff <a>..<b>.

Treat the terminal as an escape hatch: useful, but not the default.

How do I find “the commit that introduced this bug”?

From a phone, the fastest path is usually:

  • start from the file you suspect
  • scan recent commits that touched it
  • narrow to a small window

If you need a real bisect, that’s usually a keyboard task.

Can I review commit history for repos that aren’t on GitHub?

Yes.

A session works on a folder on your computer.

If the folder is a Git repo, you can review history whether it’s hosted on GitHub, GitLab, a self-hosted remote, or nowhere.

Is History read-only, or can I make changes from there?

History is a review surface.

If you decide you want to change something:

  • open Files to edit
  • then use the Git tab to review and commit (commit is an experimental Git write action, off by default)

Why are commit messages truncated on a phone?

Because the UI has to fit.

If a commit message is truncated, treat it as a signal to:

  • tap into the commit details
  • and rely more on the diff than the message

How do I review large changesets without losing the thread?

A phone-friendly trick:

  • review only the top 1–3 “risk files” first (auth, config, migrations, lockfiles)
  • leave a review comment for anything you want revisited
  • stop after you’ve made a decision

If you try to do a perfect review of 200 files on a phone, you’ll burn time and still miss things.

Can I use this workflow to review what an AI agent changed?

Yes — that’s one of the nicest uses.

If a long session made changes yesterday, History helps you answer “what actually landed?” before you decide what to do next.

When should I use a repo hosting app instead?

If the change already exists as a PR, a hosting app can be great.

The Git tab history is a good fit when:

  • the changes aren’t pushed yet
  • you’re reviewing your own local commits
  • you want the same workflow regardless of where the repo is hosted
githistorydiffsmobileworkflows
Last updated: 2026-10-26