Push261103 — Asset Update
Overview
Batch covering the whole verified range in one place:
- v2 native —
2.0.32,2.1.0–2.1.4,2.2.0–2.2.5(12 versions) - v1 native —
1.18.33–1.18.35,1.19.0–1.19.4(8 versions)
Every version ships as deb and pacman (.pkg.tar.xz): 40 assets plus
SHA256SUMS.txt.
All packages are the native family — zero-glibc Android binaries built from
upstream source (B line) with android-bun, TUI rendered by a bionic
libopentui.so rebuilt from source. No wrapper, no proot, no musl.
Verification
Every version in this batch passed the device criteria on the reference
machine (kernel 3.18.140-mokee, Android 9, aarch64):
install → --version → serve HTTP 200 → TUI frame ≥ 800 B → keystroke echo → 15 s survival → no crash/degrade markers
2.2.0–2.2.5 were re-verified for this batch on 2026-11-03; the remaining
versions were verified on the same device in their own build rounds.
Locally each package also passes verify-artifact (seccomp shim present in the
runtime binary, web UI archive embedded for v2).
Which version should I pick?
| Line | Renderer ABI | Notes |
|---|---|---|
v2 2.0.32
| opentui 0.5.17 | last of the 2.0 line |
v2 2.1.0–2.1.4
| opentui 0.6.8 | first upstream line on the ot_* context ABI
|
v2 2.2.0–2.2.1
| opentui 0.7.0 | newer renderer, TUI renamed FFI surface |
v2 2.2.2–2.2.5
| opentui 0.7.0 → 0.8.0 | 2.2.2 drops upstream @opencode-ai/pty; 2.2.3+ re-adds it as @opencode/pty, 2.2.4+ pins 0.4.0
|
v1 1.18.33–1.19.4
| opentui 0.4.5 | legacy generation, still maintained |
These are separate ABI tracks — pick by the line you need, not by "newest wins".
Do not downgrade between tracks unless you know the renderer ABI matches.
Install
# Debian/Ubuntu on Termux (deb)
pkg install xz-utils
dpkg -i opencode_<ver>_aarch64.deb # v2
dpkg -i opencode1_<ver>_aarch64.deb # v1
# Arch/pacman on Termux
pacman -U opencode-<ver>-1-aarch64.pkg.tar.xz # v2
pacman -U opencode1-<ver>-1-aarch64.pkg.tar.xz # v1opencode (v2) and opencode1 (v1) install side by side; they do not share a
runtime path.
Integrity
SHA256SUMS.txt in the assets lists every package. Verify with
sha256sum -c SHA256SUMS.txt.