Edit files on your computer from your phone

I don’t want to “develop on a phone.”

What I want is narrower:

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

…from my phone, while the repo stays on my 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 is the workflow I use to make “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:

SSH + terminal editor (vim/nano)
Remote desktop (screen sharing)
Mount a remote folder into the iOS Files app
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.

What I tried first (and where I bounced off)

SSH from my 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 me what I really want:

“I want my computer to remain the source of truth, and I want a clean phone UI for files + diffs + commits.”

A workflow that worked for me

I ended up using a “remote UI over my computer” approach.

Happier is one option that supports that approach.

It has a Projects tab where you can add folders from a connected computer and treat them as first-class projects — with:

a Files view (browse, search, download/upload)
a file editor (for small, precise edits)
a Source control view (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:

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

1) Add the repo folder as a Project

Open Projects.
Tap ADD A PROJECT.
Tap Choose a folder on your computer.
In Select Path, navigate to the repo folder.
Tap Use.

From here on, you’re working with a folder on your computer — not a copy on your phone.

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

Open the project, then open Files.

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 “I can do everything.”

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

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

After you save, switch to:

Source control → Changed files

Then:

tap ↓ Review

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

I try to make an explicit decision after each phone edit:

Keep it: it’s correct.
Revert it: I changed the wrong thing.
Leave a review comment: I want the agent (or future-me) to make a precise change later.
Commit it: it’s a self-contained improvement.

If you’re committing, you’ll see: