FoldRender / Guides / Clone a private repo on your phone
FoldRender guide

Clone a private repo on your phone

A public repository clones anonymously — that path ran on two cloud phones on 2 November 2026. A private one needs you signed in, and FoldRender offers two ways: Sign in with GitHub in the browser, or Use a code, GitHub's OAuth device flow. Use a code signed in on an emulator the same day, on an account whose repository list came up empty; the browser path was not part of that run, and no private repository was cloned. This page says so where it matters rather than at the bottom in small print.

Get it on Google Playfree See what FoldRender does

Step by step

  1. Install from Google Play

    FoldRender is on the Play Store as FoldRender: Git Repo Reader, package id dev.foldrender.app, free and distributed worldwide. Install it the ordinary way — no allow installs from this source prompt to approve, and updates arrive on their own. The app declares minSdk 30, so it needs Android 11 or newer; Play will tell you if a device is below that rather than letting you install a build that cannot run.

  2. Open the git panel

    Open the git panel and tap the gear. Sign-in sits at the top of Settings under Account, because it is the thing you do before the clone rather than after it.

  3. Path A — Sign in with GitHub

    Tap Sign in with GitHub and authorize in GitHub; the app reopens by itself. The exchange finishes on foldrender.dev, which briefly handles the token, because GitHub requires a client secret for it and an app that ships to devices cannot hold one. When it lands, Account lists your login with a Sign out button. The build on Google Play has an OAuth client id compiled in, so you get the button rather than a request to paste a client id.

  4. Path B — Use a code

    Use a code, beside the sign-in button, talks only to GitHub. The app copies a short code and opens github.com/login/device, with Open GitHub and Copy code to get back to it; you paste the code, authorize, and the token arrives on its own — the panel polls rather than making you come back. It is also what to fall back on when the exchange on foldrender.dev fails.

  5. Set a commit identity while you are in there

    On the same screen, Edit beside Commit identity opens Name and Email fields. They are written into a .gitconfig inside the app's private storage, because Android's user.home is / and is not writable — without a real home directory JGit's config loading differs between ROMs. Setting the identity is only relevant if you later commit; pushing a commit is not a verified path.

  6. Clone the private repository

    Back on the panel, tap the title. Once you are signed in your repositories are listed there, under Yours, Shared with you and each organization. Pick one, or type owner/repo into Filter, or type owner/repo and tap Open owner/repo, then tap Get the code. Credentials are looked up by host, so the same stored token serves every repository on that host. HTTPS only, because shipping a key agent is a cost the app deliberately does not pay.

  7. Read it

    From here it is identical to a public clone: the repository opens as the workspace, the tree lists (slowly on a large repository, behind a spinner with no progress indicator), and every file renders in the right-hand pane. Nothing about a private repository changes how it is read.

How FoldRender handles it

Tokens are write-only from the UI

A saved token is encrypted with an AES-GCM key held in the Android hardware keystore, and it is never read back into a field. The screen that took it clears itself, and no screen in the app displays a stored token — so a screenshot or a shoulder-surfer recovers nothing.

Why sign-in passes through foldrender.dev

GitHub documents client_secret as required on the access-token endpoint for the browser flow, and treats code_verifier as an addition to it rather than a replacement. An app that ships to devices cannot hold a secret, so a small relay on foldrender.dev holds it and finishes the exchange, and briefly handles the token. Use a code needs nothing but GitHub, if you would rather it did not.

A client id is not a secret

The identifier a GitHub OAuth app is issued is public by design; it is compiled into the build rather than being asked for. A build shipped without one falls back to a one-time field for pasting a client id, and if neither is present the panel says plainly that GitHub sign-in is not configured in that build.

What does FoldRender not do?

The honest list — shipped-but-unverified behaviour included, so you can tell before installing whether this build does the thing you came for.

How does FoldRender compare with the other ways to read a repo on Android?

Four apps people actually reach for, and the one axis that separates them: whether the repository ends up on the phone, and whether anything renders it once it is there.

ToolDownload priceWhere you get itClones to the deviceRenders PDF / notebook / MarkdownEditor or shell
FoldRenderUS$0Google Play, worldwideYes — HTTPS, anonymous for public reposYes — native Compose renderersA plain-text editor for files in a clone; no shell
GitHub MobileUS$0Google Play and the App StoreNo — it reads repositories hosted on GitHubOnly what GitHub itself renders, onlineEdits files inside a pull request
Termux + gitUS$0F-Droid or GitHubYes — the real git CLINo — terminal text onlyYes, a full shell and any CLI editor
MGit 1.7.0 (2023)US$0F-Droid onlyYes — clone, pull, push, HTTPS or SSH keysNoNo — its own listing says it ships no text editor

Prices are for the download. GitHub Mobile’s capabilities follow your GitHub plan; Termux and MGit are both free software. MGit’s version and date are from its F-Droid listing.

What are the numbers behind FoldRender?

Every figure here is read out of the shipping build or off a primary source listed at the foot of this page — nothing is rounded up for effect.

FAQ

Can I clone a private repository on Android?
The app has two sign-in paths for it — Sign in with GitHub in the browser, and Use a code, GitHub's OAuth device flow — and both are in the shipped build. No private clone has been verified end to end: Use a code signed in on an emulator on 2 November 2026, on an account whose repository list came up empty, and the browser path was not part of that run. The verified path is anonymous cloning of a public repository.
How does the GitHub sign-in work?
Tap Sign in with GitHub and authorize in GitHub; the exchange finishes on foldrender.dev, which briefly handles the token, and the app reopens. Use a code talks only to GitHub: you enter a short code at github.com/login/device and the token arrives on its own while the panel polls. Either way the panel then shows the account you signed in as.
Why does browser sign-in go through foldrender.dev?
Because GitHub requires client_secret on the token exchange for the browser flow, and an app that ships to devices cannot hold one. A relay on foldrender.dev holds the secret and finishes the exchange, so it briefly handles the token. Use a code skips it and talks only to GitHub.
Can I use GitLab, Bitbucket or a self-hosted host?
Not to clone from. Get the code fetches from github.com only, and there is no field for another host's address. Other Git hosts, in the git panel's settings, stores a token for HTTPS remotes that aren't GitHub, but it does not get such a repository onto the phone.
What happens to the token I paste in?
It is encrypted with an AES-GCM key in the Android hardware keystore and never read back into the UI. The field is cleared after saving and there is no screen that displays a stored token.
Does signing in let me push?
Signing in stores a credential. Push itself ships in the build but is unverified, so we are not telling you it works. Treat authentication as what gets a private repository onto the device to read.
How much does FoldRender cost?
US$0. It is free on Google Play, distributed worldwide, with no billing library in the build, no subscription and no paid tier.
Which Android versions does FoldRender run on?
Android 11 and newer. The app declares minSdk 30 — the API level Android 11 shipped with in 2020 — and is compiled and targeted against API 36. It is developed and tested on a Galaxy Z Fold 7, which launched in 2025.
Does FoldRender work offline?
Yes, once a repository is on the device. Cloning needs the network; reading, searching, and rendering Markdown, source, PDFs and notebooks out of a clone or a picked folder do not. Signing in to GitHub is optional and only matters for private repositories.
How is this different from GitHub Mobile, Termux or MGit?
GitHub Mobile reads repositories hosted on GitHub and does not clone to the phone. Termux and MGit both clone and then leave rendering to you — Termux gives you a shell, MGit ships no text editor at all. FoldRender clones over HTTPS and renders what it clones, on the inner screen.

Where can I check these claims?

The primary documents behind the figures above, so you can confirm any of them without taking our word for it.

Page last checked against the app's source on 2026-11-02; clean-device results on it are from an earlier pass, on an earlier build.

More FoldRender guides