Git From Your Phone: iPhone and Android (2026)

You can use git from your phone, and on Android you can run a real, current git on the device itself. The catch is that "git on phone" is really a question about where the git binary runs. On Android, Termux gives you an on-device git with pkg install git. On iPhone there is no native Linux shell at all, so a command-line git has to run somewhere else: a cloud Linux container you reach from the app, or a slow i386 emulator. This guide walks each honest path for using git and GitHub from a phone, including the full gh CLI and pull-request flow, and is current as of 2026-06-26.

This sits under our mobile coding terminal pillar. If your actual goal is reviewing and merging a teammate's work, the review pull requests from your phone guide is the focused companion. For reaching a machine you already own, see SSH from your phone, and for the wider Android dev-environment picture, the coding on Android pillar.

Why is git on a phone harder than it sounds?

git is one binary and a folder of plumbing, so in principle it runs anywhere there is a POSIX-ish shell. The friction is the operating system underneath. Android is Linux, so a terminal app can ship a normal git. iOS is not a place you get a shell: Apple's App Store rules forbid runtime fork/exec of downloaded code and just-in-time compilation for normal apps, which is exactly what a general-purpose terminal needs. That single rule is why every "terminal on iPhone" is either a remote connection to another machine or a sandboxed emulator, never a native local shell. The official git project documents the same Linux, macOS, and Windows targets and no iOS build (git-scm.com downloads).

So the real choices split by platform. On Android you decide between local (Termux) and remote (a cloud container). On iPhone you decide between a native GUI client that wraps libgit2, a slow local emulator, or a remote shell. We build the remote-shell option, so we will be straight about where the local ones are the better call.

How do you use git on Android?

On Android, install Termux (open source, GPLv3) and you have a real git in two commands. This is the genuinely free, offline-capable path, and for most git work on a Pixel or Galaxy it is all you need.

Termux ships current packages, so git, gh, and ssh all behave the way they do on a desktop. The one caveat to know is the Android 12+ phantom-process killer: the OS kills background and high-CPU processes and you can see [Process completed (signal 9)] mid-operation. A quick git commit is rarely affected, but a long clone of a multi-gigabyte monorepo can be. Android 14+ lets you disable it under Developer Options; we cover the exact toggle in the Claude Code on Android guide and the broader story in Cosyra vs Termux. The trade-off is honest: Termux is Android-only, so none of this helps an iPhone.

How do you use git on an iPhone?

On iOS there is no native shell, so git takes one of three shapes, and they are not equivalent. The first is a native GUI client. Working Copy is the well-known one: it wraps git into an iOS app and does clone, commit, branch, push, and even pull-request browsing through a touch interface. For moving commits around it is genuinely good, and on an iPad it integrates with the Files app. What it is not is a shell. There is no gh CLI, no git rebase -i in an editor, no pre-commit hook running your test script, no piping git output into another command.

The second shape is a local emulator. iSH runs Alpine Linux on iOS through i386 user-mode emulation, and apk add git gives you a working command-line git. The honest problems: the emulator carries 3-5x overhead, the app suspends about 30 seconds after you background it, which can end a clone or fetch, and the App Store build has been frozen at 1.3.2 since 2023 even though the repo stays active. git the C program runs; anything Node-based you might want next to it crashes with an Illegal instruction error (iSH issue #2335, open since 2024).

The third shape is a remote shell, which is the one that gives you the full command line on an iPhone. That is what we built, and it is the same answer as coding on iPhone generally: when the device cannot host the toolchain, you reach a Linux box that can.

Full git and gh in a cloud container

We ship git and the GitHub CLI pre-installed in every Cosyra container, because the thing that kills mobile git is setup friction, not the keyboard. The container is Ubuntu 24.04 on x86_64, so git rebase -i, submodules, LFS, pre-commit hooks, and a 4 GB clone all behave exactly as they do on a laptop. You reach the same container from a native iPhone app, an Android app, an iPad, or a browser, and it keeps running when the screen locks. BYOK applies to the AI agents we also pre-install, but git and gh are just there. We do not proxy your GitHub traffic; your SSH key and gh token live in your container.

Here is the opinion the local-tooling crowd will push back on: for anything past commit-and-push, a GUI git client on iOS is the wrong tool, and the "real terminal on iPhone" apps cannot back it with a working modern toolchain. The moment you need an interactive rebase, a hook that runs your linter, or gh pr create with a real editor for the body, you want an actual shell. On an iPhone that means a remote one. We resolve a three-way merge conflict from the train this way, and the phone keyboard is fine for it, because git is mostly short commands, not 40-line functions.

• Works when: you want the full git command line, the same on iPhone and Android, with nothing to install and your credentials persisting across devices.
• Breaks when: you have no internet. The container is in the cloud, so there is no offline mode. That is the real trade-off versus a local Termux git.
• Cost: Sign up — 1 hour free, no credit card. Extend with a 10-hour, 7-day trial when you want more. After that, $29.99/month or $300/year. See pricing.

How do you run a full git workflow from your phone with Cosyra?

You set it up in about three minutes: install the app, authenticate to GitHub once, then clone, branch, commit, push, and open a pull request. The steps below are exactly what we run on a fresh phone.

Step 1: Install Cosyra and open the terminal

Install Cosyra from the App Store or Google Play. Sign in with Apple, Google, or email and the app provisions an Ubuntu 24.04 container with git and gh already on it. Open the terminal tab.

Step 2: Authenticate to GitHub

Run gh auth login and choose the device-code flow. The CLI prints a short code, you paste it into the browser tab it opens, and you are authenticated without typing a password into the phone keyboard. The token persists in the container, so you do this once.

Step 3: Clone, branch, commit, push, open a PR

That is a complete branch-to-pull-request loop with no laptop in the room. When the screen locks the container keeps running, so the push finishes even if you put the phone away to find your seat. Reopen the app later and the repo, the branch, and your shell history are exactly where you left them.

How do the phone git options compare?

The terminal git options line up against what matters for real work: whether git installs and runs, whether you get the gh CLI next to it, whether the shell survives backgrounding, and whether it works offline. The table covers the state as of 2026-06-26. Working Copy sits outside it because it is a GUI client, not a terminal, and is the better answer when all you need is commit and push on iOS.

Choose Termux if you are on Android and want free, local, offline git and do not mind the phantom-killer caveat on long operations. Choose Working Copy if you are on iPhone and your git needs stop at clone, commit, and push through a GUI. Choose a cloud container if you want the full command line — gh, rebase, hooks, big repos — identical on iPhone and Android, which is the case we built for. For the agent side once you are in that shell, see AI coding agents on mobile.

Frequently asked questions