Edit files on your computer from your phone

A practical workflow to browse a repo, search files, make a precise edit, then review the diff and commit — all from your phone, without remote desktop.

Based on
CLI
0.2.17
Preview ref
a2c45c8

The goal is not to “develop on a phone.”

The goal is narrower:

  • fix one config value
  • tweak one line in a README
  • update a path
  • adjust a feature flag

…from a phone, while the repo stays on the computer.

Because the real pain isn’t typing.

It’s that the moment you leave your desk, file access turns into a mess of half-working options.

This guide covers a workflow that makes “one precise edit” from a phone feel safe.

The trade-offs (so you can pick your poison intentionally)

When people say “edit files remotely from iPhone”, they usually mean one of these:

  1. SSH + terminal editor (vim/nano)
  2. Remote desktop (screen sharing)
  3. Mount a remote folder into the iOS Files app
  4. Clone the repo onto the phone (a mobile Git client)

All of these can work.

The question is: which one fails least for your brain.

Common approaches and their trade-offs

  • SSH from a phone: technically fine, but it’s not a pleasant editing workflow. You end up doing real work in a tiny terminal.
  • Remote desktop: heavy and fiddly, especially on mobile networks. It’s a “break glass” tool, not a daily workflow.
  • Mounting folders into iOS Files: tempting, but brittle. It’s very easy to end up in weird states where hidden files, permissions, or tooling assumptions bite you.
  • A local mobile Git client: actually great if you want an iPad-first workflow. Working Copy is the canonical example on iOS.

But none of those options give you the combination that matters here:

The computer remains the source of truth, with a clean phone UI for files, diffs and commits.

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.

Every Happier session is attached to a folder on one of your computers, and the session gives you that folder directly. On a phone, the session opens in the mobile Cockpit, which has its own tabs for:

  • Files (browse, search, upload, download, preview)
  • an embedded editor for small, precise edits (on by default under Settings → Features → Embedded file editor)
  • Git (changed files, diffs, commit, pull/push, history)

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: edit a file on your computer from your phone

1) Open a session in the repo folder

Open an existing session that runs in the repo, or start a new one and pick the repo folder on your computer as its working directory.

From here on, you’re working with a folder on your computer, not a copy on your phone. If the session is inactive but the computer is online, Happier can still load its files.

2) Use Files as your “I just need the file” surface

In the session, open the Files tab.

Three features matter for phone editing:

  • Search (so you don’t scroll trees)
  • Download/Upload (when you need to move something)
  • An editor that’s good enough for “one precise edit”

If you see a search bar labeled:

  • Search files…

…use it aggressively.

On a phone, navigation is the tax. Search is the refund.

3) Make the smallest possible edit

Open the file you want.

Do the smallest edit that moves the world forward.

Then hit:

  • Save

If you realize you’re going down a rabbit hole, hit:

  • Cancel

A good phone workflow is not “do everything.”

It’s “do the 10% that prevents stalls.”

4) Review what you changed (don’t trust your own memory)

After you save, switch to:

  • the Git tab and its changed files

Then open the file's diff.

If the repo is large, you may see:

  • Large diff detected; diffs will load as you scroll.

That’s a clue to keep your edits small.

5) Decide: keep / revert / comment / commit

Make an explicit decision after each phone edit:

  • Keep it: it’s correct.
  • Revert it: the wrong thing changed.
  • Leave a review comment: the agent (or you, later) should make a precise change.
  • Commit it: it’s a self-contained improvement.

Committing, pulling and pushing are Git write actions. They sit behind Settings → Features → Source control operations, which is experimental and off by default according to the Git docs. Since 0.2.12 a review can select exact files for a commit, so a phone edit doesn’t have to ride along with the agent’s other changes.

If you’re committing, you’ll see:

  • Commit message
  • Commit

Try to keep commits clear and honest.

6) Push (only when you’re confident)

In the Git tab, you can use:

  • Pull
  • Push

A useful rule:

  • pull whenever
  • push only after a quick diff review

If you see:

  • Operation requires a clean working tree.

…believe it.

It’s not a suggestion.

Practical examples (what is worth editing from a phone)

These are “good phone edits”:

  • update a feature flag / config constant
  • fix a broken link
  • adjust a version pin
  • edit one env var name
  • add a TODO that unblocks future work

These are “bad phone edits”:

  • large refactors
  • migrations
  • multi-file rename sweeps

Not because they’re impossible.

Because they’re too easy to get subtly wrong when you’re away from your normal tooling.

Terminal (optional)

Sometimes you really do need a terminal.

Sessions can also show a Terminal tab when the embedded terminal is available. It’s experimental per the feature matrix and needs a connected daemon and a reachable machine.

Treat it as a last resort:

  • use the UI for files + diffs + commits
  • use terminal only when you need a command the UI doesn’t expose

If you use terminal for everything, you’ve recreated the “SSH from a phone” problem.

FAQ

Should I just use a mobile Git client?

If you want the repo on your phone, yes.

A mobile Git client like Working Copy is great.

This guide is for “the repo lives on my computer, and I just want remote edits and review.”

Does this replace an IDE?

No.

It replaces the panic moment:

“I need to change one thing right now, but I’m away from my desk.”

That’s a different job.

fileseditorgitmobileworkflows
Last updated: 2026-10-26