Browser-based graphical shell and control plane for a Linux server you own — real terminal, file manager, live metrics and BYOK AI in one mobile-first workspace. Next.js 16 · React 19 · node-pty · Tailwind v4 · shadcn/ui. Public alpha, self-hosted.
Install MSO on Android with Termux
Supported Android path: Termux hosts an Ubuntu PRoot environment, and MSO runs inside that normal Linux userspace. The
msolauncher is still installed into Termux, so normal commands remainmso,mso doctor,mso web, andmso --continue.
MSO should not be installed directly into native Android/Termux today. MSO uses Bun plus native Node modules such as node-pty; Bun does not currently support Android/Termux as a native target. Ubuntu PRoot avoids the Android libc/platform mismatch and gives MSO the same Linux environment used by the normal installer.
References:
- Termux PRoot-Distro: https://github.com/termux/proot-distro
- Bun Termux/Android support request (closed as not planned): https://github.com/oven-sh/bun/issues/29778
One-paste install
Run the canonical public installer in Termux:
curl -fsSL https://raw.githubusercontent.com/rahmanef63/mso/main/scripts/install.sh | bash
The public bootstrap detects Termux, verifies scripts/install-termux.sh, and hands off to it.
If a partial Termux package upgrade has broken curl before that command can run, use the repair
steps below first.
The Termux bootstrap is idempotent. Re-running the same command repairs/upgrades the host packages, reuses the mso-ubuntu PRoot environment when it already exists, and runs the normal MSO installer again to update the existing checkout.
Before package downloads, it rejects unsupported CPU architectures (Linux Bun requires arm64 or x86_64). On an existing checkout, it refuses to replace local commits absent from the requested ref, and will not force-move main over unique commits; preserve/reconcile those commits first.
The script deliberately does not enable YOLO mode.
What the installer does
- Runs
apt updateandapt full-upgradein Termux first. This is also the recovery path for partial Termux upgrades wherecurlcannot start because OpenSSL/QUIC libraries no longer match. - Installs
curl, CA certificates, andproot-distroin Termux. - Creates an Ubuntu 24.04 PRoot named
mso-ubuntu, or reuses it. - Creates a non-root Linux user named
msoinside the guest. - Installs Linux build/runtime prerequisites inside Ubuntu.
- Runs MSO's canonical
scripts/install.shinside Ubuntu with--no-service --no-onboard. - Installs a small Termux-side launcher at
$PREFIX/bin/msothat enters the Ubuntu guest automatically. - Verifies
mso --versionandmso -hbefore returning success.
The actual MSO installation remains owned by the normal Linux installer. The Termux script is only an Android compatibility/bootstrap layer.
After installation
Use MSO directly from the normal Termux prompt:
mso --version
mso doctor
mso
mso web
mso --continue
For first-time provider/account setup:
mso onboard
mso web is the relevant browser path because a PRoot guest does not provide a normal systemd PID 1. Keep the default loopback bind unless you deliberately configure protected HTTPS access.
If curl is broken before installation
A partial Termux upgrade can leave curl, OpenSSL, libcurl, or libngtcp2 out of sync. A typical symptom is:
CANNOT LINK EXECUTABLE "curl": cannot locate symbol "SSL_set_quic_tls_transport_params"
Repair the package set with apt first:
apt update
apt full-upgrade -y
apt install --reinstall -y openssl libcurl curl ca-certificates
Then verify:
curl --version
openssl version
If repository selection itself is broken, run:
termux-change-repo
Choose a working Main repository, then repeat the repair commands.
Why not native Termux?
Native Termux reports Node's platform as android, not linux. That distinction matters for packages that publish Linux-only native binaries. It is the same class of problem visible when installing tools such as Codex CLI directly in Termux: the JavaScript wrapper may install while an optional Linux ARM64 binary is skipped because npm sees android/arm64 rather than linux/arm64.
MSO has an additional blocker: Bun currently publishes Linux/macOS/Windows targets, not a supported Android/Termux target. Running MSO in Ubuntu PRoot is therefore the stable default rather than maintaining a growing list of native Android binary workarounds.
Codex CLI note
Codex CLI is not required to install MSO. MSO has its own model/provider integration and onboarding.
If you separately want Codex CLI on Android, prefer installing it inside the same Ubuntu PRoot environment rather than native Termux. Native Termux can hit both binary-platform and authentication/networking issues. There have also been Codex TUI reports specific to Android/Termux environments; if a future Codex version regresses in a foreground terminal, tmux inside the Linux guest can be used as a TUI workaround, but it is unrelated to the MSO installer itself.
Do not hardcode a stale @openai/codex-linux-arm64 version into MSO documentation. If a native workaround is ever needed, the wrapper and platform package versions must match exactly.
PRoot limitations
This Android installation is optimized for MSO CLI and local browser workspace use. It is not equivalent to a normal VPS:
- no normal systemd service is installed;
- host/service integrations that require systemd may be unavailable;
- long-running Android processes are still subject to Android background/battery policies;
- performance is lower than a native Linux host because PRoot translates filesystem/syscall paths in userspace.
An Android tablet can be the MSO host: MSO, its data, and compatible applications run inside its Ubuntu PRoot guest. Start mso web on the tablet, confirm mso doctor and local health, then test protected access from a second device through a private network or HTTPS tunnel. The default loopback bind is intentional: plain HTTP on the tablet's LAN IP is not a supported login path. Keep the foreground process alive, and test backgrounding, battery policy, reboot, update, storage pressure and network changes on the actual tablet before treating it as an always-on server. A separate VPS is optional; an always-on Linux host remains the better choice when the tablet fails those acceptance tests.
Security
MSO can execute commands as its Linux owner. mso --yolo automatically approves write and exec actions for that process. Do not make YOLO the default in shared/untrusted environments.
The Android bootstrap creates passwordless sudo only for the dedicated mso user inside the isolated PRoot guest so the canonical MSO installer can install Linux dependencies without interactive password setup. It does not grant Android root access.
Troubleshooting
No mirror or mirror group selected
If package operations still reach a working mirror, the warning is informational. If downloads fail, run termux-change-repo and select a working Main repository.
mso: command not found
Verify the Termux launcher exists:
ls -l "$PREFIX/bin/mso"
Then rerun the one-paste installer. It recreates the launcher idempotently.
Inspect the Ubuntu guest
proot-distro login mso-ubuntu --user mso
Inside it:
export PATH="$HOME/.local/bin:$HOME/.bun/bin:$PATH"
mso --version
mso doctor
Reset only the Android compatibility environment
Do not remove the PRoot distro as a routine repair: it contains the MSO checkout and private MSO state for that guest. Prefer rerunning the installer. If you intentionally want a destructive fresh start, back up the required MSO state first and consult the PRoot-Distro removal documentation.
Verification checklist
After installation:
mso --version
mso doctor
mso -h >/dev/null && echo "MSO CLI OK"
Then start an interactive session:
mso
For the browser workspace:
mso web
The install is considered healthy when the Termux launcher enters the Ubuntu guest, the MSO CLI resolves there, and mso doctor reports no unexpected runtime failure beyond capabilities intentionally unavailable without systemd.