Use your phone as a remote Git client
A workflow to review diffs, leave line-level comments, commit, and push from your phone — while the repo stays on a computer you trust.
- CLI
- 0.2.17
- Preview ref
- a2c45c8
The goal is specific:
- the repo stays on the computer
- changes can be reviewed from a phone
- you can make a decision (keep / revert / comment / commit)
- and you can push when you’re confident
Not because “developing on a phone” is fun.
Because the hard part of Git isn’t writing code.
It’s when you’re away from your keyboard and you still need to answer:
“Is this change OK?”
This guide covers a workflow that makes remote Git review straightforward and repeatable.
The core trade-off
Remote Git workflows always pay one of these costs:
- You mount a filesystem (SSH mounts, iOS Files providers, etc.)
- You remote into a UI (remote desktop)
- You do terminal Git (SSH/tmux)
- You keep a copy of the repo on your phone (a real mobile Git client)
All of these can work.
But they feel very different in practice.
Common approaches and their trade-offs
- SSH from a phone: works, but scrolling through long output in a tiny terminal is painful.
- Remote desktop: heavy and fiddly. Fine in emergencies, but a poor default.
- A mobile Git client that clones locally: also works — and if you’re doing “iPad-first dev”, it can be great. One well-known example is Working Copy (Git on iOS). It’s solid. But it’s not a fit when your computer is the source of truth and already has the repo and tooling.
What helps is a lighter loop: review diffs, leave comments, commit, push, without moving the repo to your phone.
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 folder on your computer. On a phone, the session gives that folder its own Files and Git tabs, so you get changed files, diffs, commits and history without a copy of the repo on the phone.
Git write actions (stage, commit, pull, push) are experimental and off by default. Turn them on under Settings → Features → Source control operations (see the Git docs). Reading status, diffs and history works without it.
Trade-off: it still depends on the computer being 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 coding workflows on a computer you trust, then manage them from your phone.
Get set up:
- GitHub: https://github.com/happier-dev/happier
- Install/download: https://github.com/happier-dev/happier#how-it-works
- Discord: https://discord.gg/W6Pb8KuHfg
Step-by-step: use your phone as a remote Git client
1) Open a session in the repo folder
Open a session that runs in the repo, or start a new one and pick the repo folder on your computer as its working directory.
2) Open the Git tab
Inside the session, open the Git tab and start on the changed files.
This gives you three practical things:
- a changed-files list
- a diff review surface
- a commit surface (with exact file selection for a commit since 0.2.12)
3) Review diffs (without rereading everything)
On Changed files, you’ll see:
- Changed files (with a count)
- a ↓ Review button
Tap ↓ Review.
If the repo is large, you may see:
- Large diff detected; diffs will load as you scroll.
That’s not a bug. It’s a guardrail: load diffs progressively instead of trying to render 600 files on a phone.
My actual phone review loop
On a phone, don’t try to do a perfect review.
Do a bounded pass:
- Open the riskiest file first.
- Decide: keep / revert / comment.
- Stop.
Most mistakes happen when review becomes unbounded.
4) Use review comments to make changes precise
This is the part many tools don’t handle well.
When reviewing on a phone, you don’t want to write a big message like:
“Please fix that part in the diff.”
Instead, leave line-level review comments on the diff.
That gives you a literal checklist anchored to:
- the file path
- the line
- a snippet of surrounding code
It’s also a great way to “queue up” work for later.
5) Commit (when you’re confident)
At the bottom of Changed files, you’ll see:
- a commit selection summary (for example: 0 files selected for the next commit.)
- an All button
- a Commit message field
- a Commit button
A small habit that helps:
- don’t commit everything by default
- select the smallest coherent set of files
- write a clear commit message that describes the intent
If the UI tells you something like:
- Operation requires a clean working tree.
…take it literally.
That message is telling you “you’re trying to run an operation that expects the repo to be clean.”
6) Pull / Push (sync with upstream)
In the Git tab, you’ll see actions for:
- Pull
- Push
If you’re doing remote Git from your phone, this is where you want to be deliberate.
A good rule:
- Pull freely.
- Push only after you’ve reviewed the diff and you’re confident.
7) Use History when you need context
If you’re trying to answer “what happened?” rather than “what changed right now?”, open:
- the commit history in the Git tab
This is especially useful when you’re reviewing a repo on your phone and you’ve forgotten what you were doing yesterday.
Terminal (optional, for the 10% case)
Sometimes you need the terminal.
Sessions can show a Terminal tab when the embedded terminal is available. It’s experimental per the feature matrix.
Strong recommendation:
- keep the default workflow UI-first (diffs, history, commit)
- use terminal for the rare cases where you truly need it
If you use terminal for everything, you’re back to “SSH on a phone”, just with nicer buttons.
FAQ
Is this “Git on my phone” or “Git on my computer from my phone”?
It’s the second one.
The repo stays on the computer.
Your phone is the review + control surface.
What’s the biggest failure mode?
The host computer goes offline (sleep, lid closed, network changes).
No remote Git client can fix physics.
The best you can do is make “is it online?” obvious and avoid workflows that silently half-apply changes.
When should I use a real mobile Git client instead?
If you truly want the repo on your iPhone/iPad (offline work, travel, iPad-first dev), use a real mobile Git client.
Tools like Working Copy exist for a reason.
This guide is for the “the computer has the repo, and I just want remote review and small interventions” case.