Sessions, not screenshots
The drawer lists every session with tags, unread weight and live status. Open one to read the transcript and keep working.
DeepSeek Harness on your phone
Pair once and read sessions, reply, approve tool calls, or open a terminal from your phone. The Host stays on your machine — no relay, no account, no cloud.
Android · open source · MIT
The drawer lists every session with tags, unread weight and live status. Open one to read the transcript and keep working.
Send a new prompt, queue it behind the current turn, or steer mid-turn. Attach an image straight from the camera roll.
Allow, always-allow or deny a tool call, and answer the agent's structured questions from the phone.
Open a real PTY for the session, keep it running in the background, and browse the workspace read-only.
Optional FCM/APNs notifications for turn end, approvals and questions; the foreground phone claims them first.
Install dsh-tag for colors and shared read state, and dsh-bag to carry skills and settings between machines.
The official browser client talks to dsh over generated Typert codecs and browser cookies. A native app cannot use either cleanly. dsh-door registers its own routes on the same Host, authenticates each device with its own revocable token, and speaks plain JSON + SSE.
On the Host: dsh plugin --profile web add dsh-door, then restart dsh web.
Open Settings → DSH Door. The terminal also prints a four-digit pairing code.
Enter the Host URL and the code in the app. The device stores its own bearer token.
No. It is an open-source plugin and client built on DeepSeek Harness; it does not modify or fork dsh.
No. The Host stays on your machine and the app talks to it directly. There is no relay or telemetry.
The codebase is React Native, but only Android is built and tested today.
The Host keeps the shell running. A floating button takes you back, and the exit prompt lets you stop it explicitly.
Tags and read state are owned by dsh-tag. Without it the app still works; titles just stay neutral.