Push261026 — v2 2.1.4 (OpenTUI 0.6.8 ABI fix) + v2 2.0.32

GitHub Release · 中文版 · English · Español · 日本語 · 繁體中文

Summary

Native family, two v2 versions, deb + pacman .pkg.tar.xz each: 4 packages + SHA256SUMS.txt. 2.0.32 is the last of the 2.0 line (opentui 0.5.17); 2.1.4 is the first 2.1 release on the 0.6.x renderer ABI (opentui 0.6.8). They are two ABI tracks — pick the line you need; they share the opencode package name, so installing one replaces the other.

Key fix (commit d7ddcb5): the first 2.1.4 build paired the 0.6.8 JS with the 0.5.x-era bionic libopentui.so, so the TUI aborted with Symbol "ot_scene_set_hooks" not found (CLI and serve were fine). The library was rebuilt from upstream sst/OpenTUI v0.6.8 (export surface diffed against the upstream glibc artifact: zero missing of 1829 symbols, no libc.so.6 NEEDED), and the build now selects it by OPENTUI_VER — unknown versions hard-fail instead of silently falling back to the wrong ABI.

Verification

On-device (Android 9 / kernel 3.18.140-mokee / aarch64): both versions report the right --version, answer serve with HTTP 200, and render a full TUI (123,184 B for 2.0.32; 101,980 B for 2.1.4, tmux capture shows banner, prompt and session list), alive past 15 s. make verify-artifact PASS for both (seccomp hardening + web UI assets); 76 shell tests ok.

Known Issues

• Only the native family ships here; compressed (UPX) and wrapper are not part of this batch. v1 stays at 1.19.3 — upstream 1.19.4 still pins effect 4.0.0-beta.83, which segfaults on the 3.18 kernel and needs the source-rebuild track first.
• Older v1 (1.18.35+) and earlier v2 TUI issues on old kernels still apply; see Push261016. 2.0.32 and 2.1.4 are verified working on 3.18.140.
• Co-installing v2 with opencode1 still needs dpkg --force-overwrite for the shared seccomp shim path; a later batch removes that conflict.

Install: pacman -U ./opencode-2.1.4-1-aarch64.pkg.tar.xz or dpkg -i ./opencode_2.1.4_aarch64.deb; verify: sha256sum -c SHA256SUMS.txt.

Full Chinese release notes: 中文版.