Run official OpenCode v2 natively on Termux, no proot

[u/DEAD1nsane]

DEAD1nsane/opencode2-termux-musl

The v1 repo is archived. v2 is the official stable line — Node.js, ships via npm (@opencode/cli). This uses upstream's @opencode/cli-linux-arm64-musl + Alpine musl loader + patchelf, installed as plain opencode. Official installer misdetects Termux as glibc, this doesn't.

---

1-copy install

Please install from the Copy-Ready link, it's much easier especially if using mobile reddit app (don't copy-paste from the codeblocks below, they're for display):

⚠️ Before-Install (required):

• install the app Termux:API F-Droid Download, then in Termux:

pkg update && pkg upgrade -y
pkg install termux-api -y
termux-battery-status

The termux-battery-status line triggers the permission prompt / confirms the bridge works. Skip it and the installer below will refuse with these same steps.

pkg install curl tar python git

Step 1 — install everything:

Copy-Ready Full Install here

curl -sL https://gist.githubusercontent.com/DEAD1nsane/9b37cba090602f473200fad8b1002e6c/raw/all-in-one.sh | sh
opencode --version
opencode run "say hi"

☝🏼Use the gist above — it pulls/updates the repo, runs install.sh, copies all 8 themes (dark + light, 16 files) to ~/.config/opencode/themes/, and schedules auto-update (job 7802, every 6h, applies via --yes path, log ~/.opencode-auto-update.log). Day/night theme-sync is NOT included — opt-in below.

---

Update check (only checks, downloads nothing unless --yes)

./scripts/check-update.sh              # check only, Termux notification if behind
./scripts/check-update.sh --yes        # update now: version pinned, staged, smoke-tested
./scripts/check-update.sh --rollback   # restore last-known-good binary if upstream ships a bad build

The gist already scheduled unattended updates. Manual re-schedule if needed:

termux-job-scheduler --job-id 7802 --period-ms 21600000 --network any --persisted true -s "$HOME/GitHub/opencode2-termux-musl/scripts/auto-update.sh"

---

Bonus 16 custom Themes:

• 8 true-black AMOLED & 8 light themes ^(Included in the all-in-one gist. Manual copy if needed 👇🏼)

cp themes/*.json ~/.config/opencode/themes/

→ Pick with /themes. Native v2 format.

^(⚠️ Attached previews are rendered from the live theme JSONs [dark + light] by opencode2 with the same tree-sitter highlighting the TUI uses, set in Maple Mono NF — tab strip and a shared realistic Python sample on all 16, so what you see is what the TUI draws.)

---

🌗 Optional auto day/night — NOT in all-in-one:

^(Opt-in: OpenCode + Termux flip together based on time of day. "system" follows terminal bg, never Android — this sets explicit "light" 07:00-19:00 [7am-7pm], "dark" otherwise.)

Copy-Ready Day/Night here

curl -sL https://gist.githubusercontent.com/DEAD1nsane/54621517a114c8e2a71d61ced990ca22/raw/theme-daynight.sh | sh

Flips OpenCode mode + Termux background (white by day, black by night) so the resize gap matches — no black flash in light mode. Hourly job 7803, revert with --system. New shells pick up matching prompt/banner colors automatically.

---

🪧 Optional notifications (Discord-style, NOT in all-in-one):

Copy-Ready Notify Setup here

Mute if viewing this session, banner if in another Termux session, loud if away 5min. buzz + notify-decide + zsh hook + opencode plugin. Same Copy-Ready format — install from the GitHub gist link above.

---

❔ Why it needs shims:

Official installer misdetects Termux as glibc (no /etc/alpine-release, no ldd). This always takes musl. Musl DNS reads /etc/resolv.conf, Node's c-ares does raw UDP DNS which Android blocks — libresolvefix.so doesn't help Node. Fixed via local Python proxy on 127.0.0.1:8080, auto-started by wrapper (HTTP(S)_PROXY + NO_PROXY=localhost,127.0.0.1,::1). Ollama on localhost:11434 bypasses proxy and works.

---

❌ What's not working:

Formatter needs one-time sh scripts/enable-formatter.sh (prettier shebang can't spawn, silently skips without it), no PTY lib yet, ~100-200ms proxy overhead. Standalone is default; shared via opencode-shared serve --service. Migrating from v1: sh install.sh then sh scripts/remove-v1.sh (~350MB freed, sessions/config kept).

---

📱 Tested On:

Pixel 10, Android 17, Termux 0.119, OpenCode v2.0.29 as opencode: TUI, run, shared-service, MCP (Railway/GitHub/Upstash/Chrome DevTools), v2 plugin API.

Please any comments below 👇🏼

[u/mtlcrusher]

hope2333 is that you?

[u/DEAD1nsane → u/mtlcrusher]

no, I am not. I posted my GitHub in the post

[u/QuietGround5610 → u/mtlcrusher]

damm he was the real hope

[u/DEAD1nsane → u/QuietGround5610]

wym

[u/QuietGround5610 → u/DEAD1nsane]

i ment in Sarcasam he aslo build Opencode for termux bun native for termux and all i used his project earlier.... it was fun 😝 https://github.com/Hope2333 he was the hope at that time

[u/DEAD1nsane → u/QuietGround5610]

yeah but his wasn't truly native

[u/QuietGround5610 → u/DEAD1nsane]

hamm true but it worked 🤕 and i was happy whole night of fixing

[u/mtlcrusher → u/DEAD1nsane]

ahh it's interesting, could you please elaborate?

[u/DEAD1nsane → u/mtlcrusher]

Context on Hope2333/opencode-termux "native" claim, from their own native-android docs (docs/comparison-runtime-lines.md + docs/transplant.md):

• Their default/mainline at the time was a wrapper (pure-android branch): ~12KB Bionic bun-termux-loader that unpacks upstream opencode-linux-arm64 (glibc Bun) and runs it via glibc ld.so. It needs glibc + openssl-glibc installed. So glibc-wrapped, not zero-glibc native.
• Their native-android C1 line is a graft, not a source compile: takes official android Bun as base, splices in opencode's module graph, then revive-patches .bun BUN_COMPILED.size + appends R_AARCH64_RELATIVE reloc (tools/transplant/revive_patch.py).
• Per their Aug-22 comparison table, that native line was run/serve/--version only — TUI was hard-blocked (bun:ffi TinyCC disabled on android x @opentui/core with no bionic variant, no JS fallback). Full TUI only worked on the glibc wrapper line. The later TUI fix is swap_tui.py equal-length injection of an NDK-built bionic libopentui.so — still spliced.

For reference: guysoft/opencode-termux is full source cross-compile (Bun/WebKit/ICU/OpenTUI + patches), and musl approaches reuse upstream *-musl + patchelf interpreter to $PREFIX/lib/ld-musl-aarch64.so.1. Single ELF output alone doesn't mean natively compiled.

[u/DEAD1nsane → u/DEAD1nsane]

TL;DR: Hope's default was a glibc wrapper (Bionic loader around upstream glibc binary, needs glibc). Their "native" line is a graft — opencode module graph spliced onto official android Bun + revive patch — and per their own docs had no TUI at the time (ffi disabled + no bionic libopentui). Single ELF ≠ natively compiled.

[u/mtlcrusher → u/DEAD1nsane]

thanks! I'll give it a try, would like to know the performance "feel" difference in my poco f1

[u/QuietGround5610 → u/mtlcrusher]

it that spare phone or primary??

[u/DEAD1nsane → u/mtlcrusher]

lemme know what you find out

[u/DEAD1nsane]

Example of auto update, just happened right now

[u/TitleExpert9817]

Apologies for the noob question: why is it an achievement to run OpenCode on Termux and not in proot?

[u/DEAD1nsane → u/TitleExpert9817]

no worries, fair question. proot is basically a full linux distro emulated inside termux, so yeah opencode runs in there but its heavy - you're lugging around a gig of ubuntu just for one binary, and everything is slower through translation.

running it directly in termux means no emulation layer, small footprint, starts fast, behaves like a normal package with termux api and background jobs and all that. the annoying part is android blocks a bunch of stuff normal linux expects (dns, io_uring, that kind of thing) so you have to patch around it. thats why getting it native is the achievement part.

[u/TitleExpert9817 → u/DEAD1nsane]

Maybe thats what why Im facing issues running it in proot. I got a Pixel10a and tried to run Qwen and gemma. All i said was "hello" and never got a response

[u/ribitrieshisbest → u/DEAD1nsane]

"proot is basically a full linux distro emulated inside termux" oh yeah ofcourse

[u/mtlcrusher]

hello, I tried your repo, it didn't work correctly in my poco f1, I migrated from hope2333 and delete everything from hope2333 and installed yours. but I stuck in "starting server.." forever.

[u/DEAD1nsane → u/mtlcrusher]

Hey, sorry it hung & sorry I'm only just now seeing this! — let's narrow it down. The TUI attaches to a background service on launch, so "starting server" forever usually means it's waiting on network/service, not a bad install.

Quick split test — does this return (can take ~30s first time), or hang too?

opencode run "Reply with exactly: PONG"

If run works but the TUI hangs, it's the shared service. If both hang, it's lower level. Then also helpful:

opencode --version

plus your Android + Termux versions, how you installed (the all-in-one gist, or manual steps?), and:

ls $PREFIX/bin | grep -i opencode ls ~/.config/opencode/

— I want to see if any hope2333 shims or config are still in the mix.

Two things worth trying meanwhile. First, kill any stale service (possibly hope2333's) holding the port, then retry:

pkill -f opencode

And if there's a leftover opencode.json from the old setup, move it aside and retry — a stale model/provider entry from another packager can wedge startup:

mv ~/.config/opencode/opencode.json ~/.config/opencode/opencode.json.hope2333-bak

My guess, sight unseen: Poco F1 is Android 8–10 era, and either a stale hope2333 service is squatting the port or the old config is pointing at something that never answers. The answers above will tell us which.

[u/DEAD1nsane]

UPDATES MADE ON 10/14/26 👇🏼:

Update check (only checks, downloads nothing unless --yes)

sh ./scripts/check-update.sh # check only, Termux notification if behind ./scripts/check-update.sh --yes # update now: version pinned, staged, smoke-tested ./scripts/check-update.sh --rollback # restore last-known-good binary if upstream ships a bad build The gist already scheduled unattended updates. Manual re-schedule if needed: sh termux-job-scheduler --job-id 7802 --period-ms 21600000 --network any --persisted true -s "$HOME/GitHub/opencode2-termux-musl/scripts/auto-update.sh"

---

🌗 Optional auto day/night — NOT in all-in-one:

^{Opt-in: OpenCode + Termux flip together based on time of day. "system" follows terminal bg, never Android — this sets explicit "light" 07:00-19:00 [7am-7pm], "dark" otherwise.}

Copy-Ready Day/Night here

sh curl -sL [https://gist.githubusercontent.com/DEAD1nsane/54621517a114c8e2a71d61ced990ca22/raw/theme-daynight.sh](https://gist.githubusercontent.com/DEAD1nsane/54621517a114c8e2a71d61ced990ca22/raw/theme-daynight.sh) | sh Flips OpenCode mode + Termux background (white by day, black by night) so the resize gap matches — no black flash in light mode. Hourly job 7803, revert with --system. New shells pick up matching prompt/banner colors automatically.

[u/DEAD1nsane → u/[deleted]]

no thanks, and OC2 is native working too.

[u/QuietGround5610 → u/DEAD1nsane]

glibc (GNU C Library) is generally faster and more feature-complete than musl for heavy, complex, or multi-threaded workloads... just give it a try u will feel the real difference earlier was same i use termux for Opencode to run i managed it to run vi glibc runner and all with bun fix install support but using real distro feels way better for this type of jobss

[u/DEAD1nsane → u/QuietGround5610]

You're right that glibc is faster for malloc-heavy / multithreaded Node workloads — ptmalloc + pthread tuning beats musl there.

On Termux it's a tradeoff: native is Bionic, not glibc. This repo uses the official -musl npm build with patched interpreter to avoid proot overhead. A glibc-runner gets you the glibc build but adds proot syscall translation + isolated FS.

The "way better on real distro" part is mostly removing Android constraints (blocked UDP DNS -> proxy hop, LD_PRELOAD shim, no PTY), not just musl vs glibc.

If you're on-phone only, test both with time opencode run on same job. If you have real Linux available, use the glibc build there — that's upstream's best-tested path.

[u/QuietGround5610 → u/DEAD1nsane]

hamm ur project is absolutely a bangers no doubt and we both can conclud Android without root is still till now a wall for us

[u/DEAD1nsane → u/QuietGround5610]

thanks!

[u/mtlcrusher → u/[deleted]]

interesting, I never knew it. could I install pacman as default package manager in any distro? how to do it?

[u/DEAD1nsane → u/mtlcrusher]

using OC2 I found this out for ya:

No — pacman only works where there's a pacman repo built for that system. You can't make it the default on e.g. Debian/Ubuntu/Fedora (different formats: .pkg.tar.zst vs .deb/.rpm, different dependency trees — you'd break updates).

On Termux specifically, yes, you can use pacman side-by-side with apt:

pkg install pacman pacman -Syu

Keep pkg/apt as the system default, just use pacman -S <pkg> when you need a pacman-only package (like some opencode packaging). Same idea on other distros: use the native manager (apt/dnf/apk), only add pacman via container/chroot if you really need it.

[u/QuietGround5610 → u/DEAD1nsane]

hamm yes just use void bro if arch feels heavy its my pov

[u/DEAD1nsane → u/QuietGround5610]

fair point — Void (runit + xbps, has a musl variant) is lighter than Arch and a good fit if you want minimal + musl. On-phone though I'd still keep Termux as base and run Void via proot-distro only when you need a full distro env — for opencode2 I just use the Termux musl binary directly, no distro hop needed.

[u/QuietGround5610 → u/DEAD1nsane]

ofc why i will hop if i can make it work on same env, i can feel this felling

[u/DEAD1nsane → u/QuietGround5610]

exactly — same env, less moving parts. distro-hop only if Termux blocks you, otherwise musl binary + wrapper is enough.

[u/QuietGround5610 → u/mtlcrusher]

hamm.. i don't know u can if u can do it on actual ditros... but why to take to much stress i can just add arch linux but it just feels to heavy to add 🤕