DEV Community

Cover image for dsh-Go Runbook: Put DeepSeek Harness on Your Phone — Pick a Mode, Wire an OpenAI-Compatible API, and Ship Safely (v1.1.0)
boluo
boluo

Posted on

dsh-Go Runbook: Put DeepSeek Harness on Your Phone — Pick a Mode, Wire an OpenAI-Compatible API, and Ship Safely (v1.1.0)

TL;DR
dsh-Go is a community, unofficial Android client for DeepSeek Harness (DSH). It runs the harness, not the model: the DSH engine runs either inside the phone (a bundled Ubuntu + Node.js environment) or on your PC/server reached over SSH / DSH Remote. Inference always goes to the API provider you configure. Checked on v1.1.0 (2026-11-15). Built from the official docs, README, and Releases page — not tested inside dsh-Go; UI details are sourced. Verified 2026-11-17.

This is a runbook, not an overview. It's grouped into five parts — Decide, Install, Wire, Operate, Fit — so you can jump to the part you're stuck on. The one thing to internalize up front: your phone never downloads model weights. dsh-Go moves the entry point and the approvals to mobile — the parts that need a human, not a GPU.


Part A — Decide

A1. Confirm you're installing the right repo. Searching "dshgo" returns several same-named projects; the wrong one is the usual mistake.

Repo What it is
ccch1mneyyy/dsh-go The Android client in this runbook
just-a-FA-for-name/DSHgo A different phone project; bundles Tailscale + a PC-side dsh plugin
@xiazhi88/dshgo A DSH plugin exposing the local web UI to a LAN
JopenChen/dsh-go A pure-Go, in-process agent implementation for backends

The one here is ccch1mneyyy/dsh-go, AGPL-3.0 (sdk/ and examples/ are MIT); the README states it is community, unofficial, and unaffiliated with DeepSeek. Several forks reuse the name — download only from the original Releases or official download page.

Spec Value (checked 2026-11-17)
Version v1.1.0, 2026-11-15
Platform Android 8.0 (API 26)+; iOS in development, no public build
APK dsh-go-1.1.0-arm64.apk, 221 MB; no 32-bit ARM or x86_64 in this release
Distribution APK sideload

dsh-Go v1.1.0 Releases page

A2. Why a phone can host it at all. DSH (dsh) is DeepSeek's open-source agent framework — MIT, TypeScript, "technology preview." Its model is "Agent = Model + Harness": sessions, tools, permissions, and the agent loop are swappable plugins, and it's model-agnostic. The phone runs that engine, which only approves tool calls, reads/writes a workspace, and talks to an API — no local compute. The trade-off: DSH is a preview, so the client chases it; the v1.1.0 notes say voice, the floating bar, Do-Not-Disturb, and the proot upgrade passed only automated tests and builds, not a full run on real hardware.

A3. Local vs remote — decide where the engine runs. This is the first real choice; everything downstream (channels, workspace, plugins) belongs to that host.

Local Remote
Engine Bundled Ubuntu + Node.js on the phone DSH on a computer/server
Prereqs ~1 GB, no root, no Termux DSH installed remotely; SSH open or remote plugin
Phone control Yes (local engine, normal mode) No
Best for Light text, small scripts Taking over long jobs, code triage

Rule of thumb: have an always-on machine → go remote (also recommended when phone storage/memory is tight); install local only to work entirely on the phone. Remember: local is not offline — both modes bill against your provider account; and config follows the host, so re-check after switching.


Part B — Install & connect

B1. Download and verify. Get the arm64 APK from Releases or the official page, allow the install source. Verify the hash — published SHA-256 for dsh-go-1.1.0-arm64.apk is ec7d9ffbfb6cf3d5d8b0c19cd34a5933df00b9290cfe9d6dbdc05337308b3037, matching SHA256SUMS in the release; compare on a PC with PowerShell's Get-FileHash. The hash changes every version — use the page's value on the day. A differently-signed APK can't overwrite an install; uninstall first (which wipes chats, the Linux environment, and settings). Background survival is unreliable; disable battery optimization under Background running, and expect the OS may still end it.

B2. Connect a remote host (if you chose remote).

  • SSH — host needs DSH (npm i -g @deepseek-ai/dsh) and SSH open; add under Settings › Remote hosts; managed start uses dsh web; verify the fingerprint on first connect.
  • DSH Remote — no network setup, end-to-end encrypted; install the remote plugin on the host and log in, then log in on the phone with the same account. It's a separate OSS project, ds-harness-remote (github.com/liguobao/ds-harness-remote), protocol-compatible with dsh-Go. Over DSH Remote you can only send images; the in-app web view, DS Bot, and log export are off, and plugins are toggle-only.

Part C — Wire a model

Keep four things separate: protocol, Base URL, API Key, model ID. The provider name is a label; those four decide how requests are sent.

C1. Pick a key source.

  • Official, direct to DeepSeek — create a key at platform.deepseek.com; the official DeepSeek card in Settings › Models takes it directly, no Base URL. Its list tracks DeepSeek's published models (background refresh ~every 10 min); doc examples name deepseek-flash and deepseek-v4-pro, but trust your account's list.
  • Aggregator, Crazyrouter as the example — one endpoint and key across several vendors. Sign up or log in; create a key in token management, named per device — the full key shows once, so after copying never paste it into a screenshot or chat; check expiry, quota, and model limits; copy a model ID from the catalog. The examples here are deepseek-v4.1-flash and qwen3.8-flash, this platform's own names, distinct from DeepSeek's official names — don't mix them.

Crazyrouter console API Keys page, key value masked

C2. Add the channel (Settings › Models › Add channel): protocol OpenAI for an OpenAI-compatible endpoint — it's a wire format, not a limit to OpenAI's models; fill Base URL and API Key; Base URL ends at /v1 — don't append /chat/completions — here https://api.crazyrouter.com/v1; Fetch models and select, or Add manually and type the model ID verbatim; save with at least one model.

dsh-Go: add custom channel, four steps

DSH official provider docs: custom model API form

Gotchas: a channel belongs to the current host and doesn't travel; Provider ID is permanent (requests, saved sessions, default model, credential refs all use it) — rename = new + delete old; one provider, one protocol; since v1.0.16 custom channels support custom headers (also for model discovery); resetting the runtime deletes custom channels and restores only the saved DeepSeek key.

C3. Verify in three layers — don't let one button stand in for the rest:

  1. Read the model list (Fetch models / Test connection). The guide: Test connection "reads the model list with the saved key, without spending tokens" — it only proves address + key line up.
  2. One short reply — confirms the basic request.
  3. One small tool task — have it list the files it will read, extract TODOs, then decide to write. Only this exercises streaming, tool calls, and approvals.

dsh-Go guide: Test connection note

When it fails, hit the endpoint from a terminal first to split channel from client. Generic OpenAI-compatible shape below; not tested inside dsh-Go, so verify with a small budget, and keep the key in an env var, never on the command line (PowerShell: $env:CRAZYROUTER_API_KEY):

curl -s https://api.crazyrouter.com/v1/models \
  -H "Authorization: Bearer $CRAZYROUTER_API_KEY"
Enter fullscreen mode Exit fullscreen mode

C4. Error quick-reference (from the official "Configure models" troubleshooting and the dsh-Go guide):

Symptom Check first
Fetch models → 401 Key complete, belongs to current Base URL; discovery calls GET /models
Wrong format / empty list Format outside the probe's range; add model IDs manually
UNKNOWN_MODEL Select a configured model, or add the missing one
MISSING_CREDENTIAL Store the key via the model page, or supply the referenced env var
Key + URL correct, every request rejected Gateway's request shape differs from OpenAI's: set compat.supportsDeveloperRole: false and compat.maxTokensField: max_tokens in the host's cordis.patch.yml
App chats, headless → MISSING_CREDENTIAL dsh --profile headless ignores the app's saved key; set an env var or .env

DSH official provider docs: troubleshooting list

Cost note: an agent loops and re-feeds tool output into context, so one task usually costs more tokens than plain chat. Use a per-device key with a quota cap, start small, reconcile against the console.


Part D — Operate safely

The README's own line: tools have real effects and the confirm/block machinery can't remove all risk — keep defaults, grant only what's needed.

  • Download only from official sources and verify the hash; sideloading has no store review.
  • Keys: one per device with a cap, never in chats, issues, or screenshots; the diagnostic bundle tries to strip keys, but check before sharing; on suspected leak, revoke first, then review usage.
  • Data path: local ≠ offline; prompts and file contents go to your provider, and through the aggregator when used.
  • Phone control: on-screen text may go to the model, screenshots to vision models (card/ID numbers masked first); passwords, codes, and payments are handed back to you by default — don't "lift limits" on a device holding payment data; a dark screen stops the task, three idle minutes ends it; Android Shell needs separate authorization and per-command confirmation.
  • Least privilege & injection: the AI can be misled by malicious instructions in pages, messages, or files; use a limited dedicated account remotely, not root; approve high-risk steps; never run irreversible tasks unattended.
  • Plugins: market risk labels "do not guarantee safety"; install scripts run on the target host, so read the package list before allowing; a plugin's first read of the input box, clipboard, or a reply prompts you, and the grant can't be individually revoked.
  • Telemetry: anonymous stats on by default (versions, device model, counts, token totals since 1.0.17; no account, key, chats, host address, or model), toggled off under Privacy & sharing; phone control's Google ML Kit has its own SDK stats; "auto failure analysis" is off by default.
  • Connections & sharing: verify fingerprints on first SSH / DSH Remote connect; credentials stay in the phone's secure storage; read the official "public deployment" chapter before exposing the web service; share links are end-to-end encrypted but anyone with the full link can read them; reset and uninstall wipe local data irreversibly.

dsh-Go README: risk notice and disclaimer

dsh-Go FAQ: what the app sends


Part E — Fit

Features (v1.1.0): model/thinking-effort switching, images, voice input, tool approvals, steering and queued messages; a web mode mirroring one conversation; end-to-end encrypted replay links; phone control; new voice calls; plus pets, tavern, scheduled tasks, terminal, and workspaces.

Plugins come from a built-in market (Official / DSH-Go-compatible / All). Community lists (such as awesome-dsh-plugin, github.com/bruc3van/awesome-dsh-plugin) frequently name dsh-web-ui / DSH-better-sidebar (UI), dsh-at-file (@file), modlens (vision), dsh-websearch (search), dsh-layered-memory (memory), dsh-api-dashboard (usage), and dsh-plugin-gate (scans scripts, permissions, keys, network callbacks before install). A plugin's native UI needs a dsh-go bridge on the host — local has it, remote usually doesn't — so check the "DSH-Go-compatible" tag.

dsh-Go guide: plugin market risk labels

For you if: you're already on DSH and want to approve/take over jobs away from the desk; you have an always-on machine via SSH or DSH Remote; you'll start with read-only, small-folder tasks and widen access gradually.

Not yet if: your device holds payment/banking data (don't lift phone-control limits); you want irreversible tasks running unattended; you expect an offline local model; you're iOS-only.

Limits: unofficial and tied to a preview DSH, so behavior can shift between versions; some new features only passed automated tests and builds; DSH Remote is feature-limited; background survival isn't guaranteed; the code is AGPL-3.0 while the name, logo, and mascots are outside the open-source grant, and forks must credit the main repo and author. This runbook was not tested inside dsh-Go; UI and flows follow the official docs and project guide, and third-party plugin descriptions come from community lists, not individually verified.

Bottom line: dsh-Go isn't "a large model in your pocket" — it moves DeepSeek Harness's entry point and approvals onto the phone, trading DSH's split architecture and plugin model for mobile flexibility while taking on a preview framework's version churn and permission surface. Safe order: verify the APK → start with remote or a read-only task → one capped key per device → pass the three-layer check → then add plugins and more privilege.

Sources

Verified 2026-11-17. Versions, hashes, model IDs, and page content change; rely on the official pages on the day.

  • dsh-Go repo, README, Releases, SECURITY.md: github.com/ccch1mneyyy/dsh-go
  • dsh-Go guide (same repo, docs/guide/): models and channels, engine and remote hosts, phone control, plugins, troubleshooting
  • DeepSeek Harness repo github.com/deepseek-ai/deepseek-harness; official "Configure models" docs deepseek-harness.github.io/deepseek-harness/guide/providers
  • DSH Remote: github.com/liguobao/ds-harness-remote
  • awesome-dsh-plugin curated list: github.com/bruc3van/awesome-dsh-plugin
  • Crazyrouter site: crazyrouter.com; sign-up, token, and model-catalog entries checked November 2026

Top comments (0)