dsh-mobile-apk README

The project's README from github.com/kelai141/dsh-mobile-apk. As one markdown file: README.md.

dsh-mobile-apk — DeepSeek Harness Android Shell APK

🌐 中文说明 / 中文 README

DeepSeek Harness Android

dsh-mobile 生态 · dsh-shell-termux（shell）· dsh-client-ui-responsive（移动 UI）· dsh-host-web-compat（浏览器兼容）

0.13.0 — official release: the ADB real channel (pairing / port discovery / shell execution / authorization gates / audit) is fully implemented and device-verified.

  • Plugin-marketplace caveat: the built-in marketplace covers many third-party plugins, and most of them are likely unavailable or buggy on phones (mobile vs desktop differ in WebView engine / filesystem / permission model / runtime). Mobile adaptation is long-term work — treat this beta as usability validation & feedback, not a production dependency. Report plugin issues to the issue tracker with device model / version / reproduction steps.

Android shell for DeepSeek Harness: WebView UI over an embedded Termux runtime snapshot (extract-and-run, no Termux app needed), SAF directory bridge, keep-alive foreground service, engine watchdog, and online runtime updates. One APK to install: it boots a full dsh web agent that can really execute bash. App name DeepCode (icon text DeepSearch), package com.dsharnessmobile.shell, version 0.13.0-fx-1 (versionCode 26).

Features

Download / Install

Release v0.13.0-fx-1 ships two ABI variants (plus snapshot archives, plugin packages, MANIFEST checksums and release notes):

APK Target
dsh-mobile-apk-v0.13.0-fx-1-arm64.apk arm64 devices (real phones)
dsh-mobile-apk-v0.13.0-fx-1-x86_64.apk x86_64 emulators / devices 
adb install -r -t <apk>    # same-signature overwrite install

ABI must match the device. A mismatched snapshot crashes the engine at startup — node ELF EM_X86_64 vs EM_AARCH64. Pick arm64 for real phones, x86_64 for emulators.

Build

Snapshot build & packaging live in the coordination repo (dsh-mobile); this repo is the shell. Requirements: JDK 17+, Android SDK (compileSdk 36); Gradle 8.11.1 via wrapper.

# Snapshot build (Termux sources + dependency closure + pnpm + cordis overrides + slimming):
node scripts\build-snapshot-013.mjs <arm64|x86_64>

# One-shot packaging (snapshot → injection → gates → gradle):
pwsh scripts\build-apk-013.ps1 -Suffix "-preview"
# output: out\v0.13.0\dsh-mobile-apk-v<ver>-<abi>.apk

Gates (inside build-apk-013.ps1): third-party compliance (check-third-party.mjs, GPL obligations) / secrets / ELF / cordis mount-set ⊇ injected set / LICENSES self-check (Python streaming) — any failure rejects the build.

Bridge protocol v1 (window.androidBridge)

App name DeepCode (icon text DeepSearch), package com.dsharnessmobile.shell. androidBridge.version returns the app version (currently 0.13.0-fx-1, versionCode 26); pages feature-detect on it. The ADB methods below are the preview authorization surface — the real channel completes in the 0.13.0 official release.

Synchronous

method signature description
version () → string app version (0.13.0-fx-1) for feature detection
getSystemDark () → boolean system dark mode (bypasses vendor WebViews whose matchMedia is stuck on light; used by the first-frame theme bridge)
checkEngine () → string probes 127.0.0.1:3080; JSON {running, latencyMs, error?}
hasAllFilesAccess () → boolean whether All Files Access is granted (external workspace requirement)
getPickToken () → string one-shot token for the directory-picker bridge (validated by the engine-side pick endpoint)
copyText (text) → boolean native clipboard write (WebView clipboard.writeText is always rejected; page falls back to this)
getDevLogEnabled () → boolean dev debug-log toggle state
getAdbState () → string ADB authorization state view (gate state machine): JSON {fullAccess, allowSwitch, paired, wirelessDebugOn, message} (preview)
discoverAdbPorts () → string wireless-debug port auto-scan (native TCP sweep): pairing-port candidates as JSONArray; [] while wireless debugging is off (preview)
setAdbPair (code, pairPort, connectPort) → boolean gate-3 pairing: real adb pair handshake; the code goes to argv only — never into the audit log (preview)
adbShell (cmd) → string ADB shell primitive: JSON {ok, stdout?, stderr?, guidance?}; fail-closed when not authorized (preview)

Commands

method signature description
keepScreenOn (enable) screen-on wake lock
showNotification (title, text) test notification channel (POST_NOTIFICATIONS)
pickDirectory (callbackId) SAF tree picker; result async via window.__dshBridge.onDirectoryPicked(callbackId, path)
pickImage (callbackId) SAF image picker; result async via the same callback
setTextZoom (percent) WebView font scale (50–200; Settings → General slider)
setImmersiveMode (enable) immersive status bar toggle (true = status bar normally hidden)
downloadDebugLogs () exports engine logs + environment info (zipped, system download/share dialog)
requestAllFilesAccess () opens the system All Files Access grant page (special permission)
restartEngine () restarts the engine process (EngineService watchdog brings it back)
shutdownToGuide () stops the engine and falls back to the test screen (no auto-restart)
reloadWebUI () reloads the Web UI
openConsole () opens the built-in console
setDevLogEnabled (enabled) sets the dev debug-log toggle (logs go under dshdata/log/ when on)
setAdbAllow (enable) gate-2 "allow access" switch (default off; off ⇒ channel fail-closed) (preview)
revokeAdbPair () revoke pairing (disconnect + delete adbkey + clear state; audited) (preview)

The bridge decouples the APK from the dsh version: pages feature-detect on androidBridge.version.

Online update protocol

  1. App fetches manifest.json: {url, sha256, size} (default http://10.0.2.2:8899/manifest.json for emulator testing; production points at a release server);
  2. Downloads the snapshot, verifies SHA-256, extracts to a staging dir (never touching the live tree), atomically swaps usr → usr-old → new usr, then kills the old engine — the watchdog restarts it from the new runtime.

Test trigger: adb shell am start -n com.dsharnessmobile.shell/.MainActivity -a com.dsharnessmobile.shell.action.UPDATE; status is written to files/update-status.txt. Test server: serve manifest.json + the snapshot from any local HTTP server (default endpoint http://10.0.2.2:8899/manifest.json maps the host from the emulator).

Permissions

permission purpose
INTERNET WebView + engine probe
POST_NOTIFICATIONS notification channel (runtime request on API 33+)
FOREGROUND_SERVICE + FOREGROUND_SERVICE_DATA_SYNC keep-alive foreground service
MANAGE_EXTERNAL_STORAGE All Files Access (external workspace requirement; special permission, user-granted)

SAF picking needs no permission.

ABI & pagesize

arm64 and x86_64 are both verified end-to-end; APKs are distributed per-ABI (the embedded snapshot is arch-specific). A 16KB-page build must be produced on a 16KB device (see docs/design.md §ABI).

License

MIT. Contains third-party components under their own licenses (see dependency declarations). GPL compliance: copyleft license texts ship in all three forms — snapshot usr/share/LICENSES/, repo LICENSES/, and APK assets/licenses/. Design rationale: docs/design.md.

Acknowledgments & invitation

Thanks to the community for feedback and contributions — especially cdwlll (environment issues), haitunlang (MIUI 12 compatibility), TACONailoong (legacy-WebView compat), X-SCI-TECH (PRs), Yangerwei (file race feedback), gr12-cmd (armv7l demand), cmyfqwq (coverage-install compatibility feedback).

Contributors welcome: Android compatibility testing (Huawei / Honor / Xiaomi custom WebViews), armv7l and more device support, completing the ADB channel, and growing the plugin ecosystem. Development & contribution guidelines live in each repo's AGENTS.md.

dsh-mobile-apk (kelai141/dsh-mobile-apk)

dsh
Searching Database…

750 ·GitHub
Dsh-mobile-apk
What is this?This is 'dsh-mobile-apk', an Android shell app for DeepSeek Harness (dsh): a WebView UI wrapped around an embedded Termux runtime snapshot, giving you a full dsh web agent on your phone that can really execute bash, no desktop or separate Termux app required.
Is this a standalone app, or do I need Termux installed separately?It's one self-contained APK (app name DeepCode) that bundles its own Termux runtime snapshot — node, git, bash, coreutils, dsh, plugins, pnpm, python/perl/ruby — so no separate Termux app is needed.
Do I need to pick the right APK variant for my device?Yes — the ABI must exactly match your device; installing the wrong variant (arm64 vs x8664) crashes the engine at startup instead of just failing to install.
Does the plugin marketplace work well on phones?Not reliably yet — most third-party plugins in the built-in marketplace are likely unavailable or buggy on mobile because WebView engine, filesystem, and permission models differ from desktop; the project treats this as a beta usability test, not a production dependency.
Does it need an internet connection to run?No — once the runtime snapshot is extracted, the dsh engine runs fully offline; internet is only needed for the optional online runtime-update manifest.
What permissions does the app need?It requests INTERNET and POST_NOTIFICATIONS, foreground-service permissions for its keep-alive engine service, and MANAGE_EXTERNAL_STORAGE ('All Files Access') for the external workspace; SAF directory picking itself needs no extra permission.
What is the ADB real channel for?Added in 0.13.0, it pairs with the device over wireless debugging (adb pair SPAKE2 handshake plus mDNS port discovery) and runs shell commands via adbd, gated by a three-step authorization flow (All Files Access, an in-app switch, pairing code), a danger-command blacklist, and an on-device audit log.
What happens if the main dsh engine crashes?A built-in standalone bash console (backed by the embedded Termux) stays usable for diagnostics even when the engine is down, and a 5-second watchdog plus crash auto-rollback gate try to restart it automatically.
Can the runtime update itself without a new APK install?Yes — it fetches a manifest.json with a URL and SHA-256, downloads and verifies the new snapshot, atomically swaps it in, and restarts the engine, all without needing an APK update.
What does the File-to-session (F5) feature do?Opening a file via Android's Share/Open-with jumps into the app and starts a fresh temporary workspace session for that file, which auto-cleans up after a 7-day TTL.
What are similar projects?dsh-mobile, DSHA, deepseek-harness-android-app, termux-app, dsh-undo-savepoint, my-tv-webview, Podroid, dsh-desktop
Which topics is it in?termux, webview, bash, android-app, dsh, harness, dsh-plugin, kotlin, deepseek-harness, mobile-app, shell, offline
Creator
kelai141
Size
35.1 MB
Stars
750
Updated
CommitOct 18Releasev0.14.8Oct 17
Age
2mo
Commits · 90 Days