dsh runs on Termux (Android) — with 5 small patches

[lilyco-42]

dsh runs on Termux (Android) — with 5 small patches

Hi team! First of all, thank you for @deepseek-ai/dsh — I'm literally running this session on Termux (Android) right now, powered by dsh.

The catch: npm install -g @deepseek-ai/dsh installs but does not run on Termux. Five independent incompatibilities have to be fixed. I've packaged everything into a one-command installer: lilyco-42/dsh-termux.

The 5 problems and their fixes

#	Package / feature	Problem	Fix
1	node-pty	node-gyp copies process.config.variables.OS = "android" into config.gypi, making gyp reference the undefined android_ndk_path.	Patch node-gyp to drop the OS variable so gyp infers linux.
2	koffi	base.cc calls statx(), hidden by bionic below API 30; clang targets android24.	Compile with --target=aarch64-unknown-linux-android30.
3	sharp	No prebuilt binding for android-arm64.	Install system libvips and build sharp against it (SHARP_FORCE_GLOBAL_LIBVIPS=1).
4	HMR service	cordis-plugin-hmr needs Node --expose-internals; node-addon-require-builtin has no android prebuild.	Rewrite the dsh shebang to node --expose-internals.
5	session-persistence-jsonl	Publishes logs with a hard link(), forbidden on Android (EACCES).	Switch the atomic publish to rename() (equally atomic).

Install (Android 11+/API 30+)

bash <(curl -fsSL https://raw.githubusercontent.com/lilyco-42/dsh-termux/main/install.sh)

Verify

dsh --version
dsh web            # serves the browser UI
dsh --profile headless "hello"   # one task, prints result, exits

For the maintainers

• Are there plans for official Android/Termux support in the harness? Happy to help port these patches into the repo (I know CONTRIBUTING.md currently says external PRs aren't accepted yet — just wanted to document the work in the recommended channel).
• Items 4 and 5 are genuinely portable to the upstream source (bin.js re-exec with --expose-internals, and rename() over link() in the JSONL session persistence), and would benefit non-Termux users too (e.g. link() also fails on some filesystems).
• Items 1–3 are install-time concerns (node-gyp OS detection, clang target, sharp prebuilds) that could be handled by a small install helper shipped with the CLI.

Thanks again for building this — the plugin architecture is a joy to work with on mobile. 🙂