deepseek-harness-phone-remote
In a curated listMaintenance: Activezetaluolang-cyber/deepseek-harness-phone-remote
DeepSeek Harness phone remote control via Tailscale - persistent file/workspace plugin - tested on OPPO Find X8 Ultra
$ dsh plugin add deepseek-harness-phone-remoteInstall
dsh has no central install command — add this plugin’s entry (documented in its README) to your profile or patch config, then restart.
How installs work10
stars
0
forks
JavaScript
Language
MIT
License
2026-08-15
Created
2026-09-08
Last push
README
DeepSeek Harness Phone Remote
Don't watch your agent. Keep its pulse.
A secure, zero-app remote workspace for DeepSeek Harness. Reach the real Harness web UI from your phone over Tailscale (or LAN), manage files and workspaces, and keep an ambient eye on your agents through Agent Presence — the floating Orb, Task Board and notifications.
- 🎈 Agent Presence — floating brand Orb (drag anywhere): Needs You / Failed / Possibly Stalled / Running / Done / Idle / Disconnected, with a Task Board and browser notifications for what needs you.
- 📁 Files & workspaces — start/resume an agent in any approved folder; read, write, upload, download files.
- ↔ Handoff — leave the desk and continue the same session from your phone
(
sessions.open— never a replacement session). - 🔐 Device pairing — one-time code, per-device credentials, revocation.
This project does not replace the Harness UI. It turns Harness itself into a remote work environment: the phone opens the real DeepSeek Harness web UI over Tailscale (or your LAN), and a persistent plugin bridges the gaps a browser can't close remotely — authenticated file/workspace access and Agent Presence (Orb / Task Board / notifications).
[!WARNING] Device pairing authenticates this plugin's
/remfsand protected/api. Treat tailnet/LAN reachability as access to the Harness control plane; keep walk-on-LAN off unless needed and restrict Tailscale ACLs to trusted devices.
English | 中文 · Architecture · Security · Contributing
Why
- Harness binds
127.0.0.1— a deliberate, sane default. The Harness process itself stays loopback-bound; only the opt-in forwarders (Tailscale IP and, when enabled, the LAN IP) expose selected interfaces. - A phone browser still can't reach loopback, and the GUI's directory picker is a loopback-only privileged method — so this plugin adds a secure path (Tailscale + LAN forwarders) and a filesystem/workspace bridge for exactly those two gaps.
- Sessions normally die with the page — this plugin is a persistent loader entry, so the workbench loads on every page automatically, no per-session "run" needed.
Architecture
flowchart LR
P[Phone / remote browser] -->|Tailscale HTTPS| S[tailscale serve]
P -->|Tailscale IP| T[TCP forwarder]
P -->|same Wi-Fi: LAN IP| L[LAN forwarder]
S --> H[DeepSeek Harness Web<br/>127.0.0.1:3080]
T --> H
L --> H
H --> R[/remfs RPC channel<br/>trusted-host fence/]
R --> A[Device authentication<br/>pairing + per-device credential]
A --> F[Filesystem capability layer<br/>allowlist + protected paths + realpath]
F --> W[(Approved workspace)]
Three independent layers:
- Transport — who can reach the channel: Tailscale membership or your LAN (forwarders only bind the Tailscale IP and the LAN IP; never 0.0.0.0).
- Application — who may use it: device pairing + per-device credentials.
- Capability — what they may touch: the allowlist + protected paths.
trusted-host and the tailnet are transport trusts. They are not
authentication. Pairing and the filesystem capability layer are.
Features
More in Other
dsh-oil-creator
by oil-oil
AI-assisted local creator workbench for DeepSeek Harness
dsh-novel-writer
by akira399
网络小说创作插件:九阶段门禁式创作流程 + 世界书设定注入 + 本地书籍导入 + AI 一键润色 + 去 AI 味。
dsh-multica-runtime
by multica-ai
Support dsh runtime on Multica.
dsh-plugin-radar
by adamplatin123
An ecosystem radar for the DeepSeek Harness (dsh) plugin community that auto-discovers thousands of candidate plugins and runs continuous k8s-level validation, publishing the results as a browsable plugin catalog.
