liguobao/deepseek-harness-remote

English  ·  中文  ·  Documentation  ·  Web  ·  Android  ·  iOS

Self-hosting  ·  npm  · 

Remote mode supports the official plugin page for listing, configuration, and enabling/disabling plugins (requires an updated Host Remote plugin). Remote itself remains locally managed on the Host; remote installation and removal are not exposed.

Connect once. Ready whenever you are.

Continue using your DeepSeek Harness instance from a phone, computer, or browser. Return to the same Harness session from whichever device is with you.

Harness keeps running on your work computer, with the same workspaces, tools, and project setup.

DS Harness Remote is simply another window into that environment.

The DeepSeek Harness desktop edition is supported. Install the latest release:

ds-harness-remote@0.5.18

Contents

• Connect once. Ready whenever you are
• Features
• Supported clients
• Install
• Quick start
• Screenshots
• How it works
• Experimental ACP workspaces
• End-to-end encryption
• Network and transport
• Security
• FAQ
• Documentation
• Links
• Star History
• Project status and trademarks
• License

Features

Harness automation tasks are available through the native Desktop/browser UI over Remote: view tasks and delivery history, edit timing/name/instructions, and delete tasks. Create tasks through the official schedule_create Agent tool. Tasks remain stored and executed on the Host; update the Host Remote plugin to enable management.

• Access your local Harness instance remotely from the web, a PC, or a mobile device: DSH first, with Codex, Cursor, and Antigravity support too.
• Use the native DeepSeek Harness interface without a separate desktop conversation UI.
• Create workspaces, configure models, and switch conversation models with the same smooth workflow as local use.
• Support DeepSeek Harness Desktop, ready to use after installation.
• Run a terminal-only dsh-TUI profile as a Host.
• No public listening port or public IP is required on the Harness Host. Connect from anywhere with internet access over a bidirectional end-to-end encrypted channel.
• Prefer P2P connections, use TURN relay nodes worldwide, and fall back to Server Relay when needed.
• Access workspace files, read-only previews, remote terminals, and authorized local development-service previews through the native Harness sidebar.
• CodeX and ACP terminals use the Host's default shell in the session directory and restore the terminal screen on reconnect.
• Android keeps per-conversation drafts and reading positions, offers backend-separated search

and local favorites. Conversation text is loaded from the connected Host.

Supported clients

Client · Form · Status · Notes DSH Desktop plugin · Remote sidebar inside DeepSeek Harness Desktop · Supported · Install ds-harness-remote@0.5.18; this computer can also be the Host Remote Web · Browser page · Supported · Open dsh.r2049.cn/app; reuses the native Harness interface Android · Native app · Supported · Download the APK from Releases; see the Android guide iOS · TestFlight beta · Beta · Not publicly released; see issue #20 VS Code · IDE extension · Experimental · Sign-in, Host fingerprint pinning, workspace-to-session navigation and prompts; streaming updates, automatic reconnect and the question UI are still in development, and cross-machine end-to-end validation is not finished Browser extension · Chrome / Edge MV3 extension · Entry point only · Exchanges an already signed-in Web authorization for a separate device credential, lists online Hosts and opens the same-origin Remote Web; it does not host a conversation UI dsh-TUI · Terminal-only CLI profile · Supported · Can act as a Host; see the dsh-TUI Remote guide. The installer never creates a Web service for it automatically

Several clients can connect to the same Host at once; RPC calls and streams are isolated per connection.

Install

DeepSeek Harness Desktop support

Open Extensions / Plugin management in DeepSeek Harness Desktop, choose installation from npm, and enter this package:

ds-harness-remote@0.5.18

Restart Desktop afterward. Its official dsh launcher can also install the pinned package with dsh plugin --profile desktop add -w ds-harness-remote@0.5.18.

dsh-TUI Host

For terminal Host setup with dsh-TUI, see the dsh-TUI Remote guide.

Command-line installation

Add the exact package version through DSH's plugin manager for the web profile:

dsh plugin --profile web add -w ds-harness-remote@0.5.18

Restart DeepSeek Harness after installation.

For CLI installation, use dsh plugin to install the npm package into the selected profile and add its bundle configuration layer.

Plugin installer

The sole installer is scripts/install.sh:

• Linux: requires root; reuses an existing DSH or bootstraps private Node.js/DSH, accepts a one-time Host registration token, and enables/starts a systemd system service. The Host and remote tools run as root; grant access only to trusted accounts.
• macOS: run as a normal user; reuses Desktop's official launcher or an existing CLI, without installing DSH or creating services.
• Windows users use official Plugin management or existing Harness commands; no Windows installer is provided.

See the installation guide for private token input, updates, service controls and validation limits. Repository changes do not automatically deploy the hosted installer.

Android client

Download the latest APK from GitHub Releases, sign in to the same account, and select a Host and workspace to continue your conversation.

iOS client

• Join the beta

Quick start

1. Open Remote from the Harness sidebar.
2. Sign in with a GitHub or Zhihu QR code, or use your account and password.
3. The Host starts with control of the current computer enabled. Remote terminal access is also enabled by default; you can turn it off in the detailed Remote settings.
4. On another device, open the DeepSeek Harness desktop edition, Remote Web, or the Android client and sign in to the same account.
5. Select the online Host, then choose an existing workspace or browse remote directories to open one.

By default, Remote uses this project's hosted Server at https://dsh.r2049.cn.

For self-hosting, use the repository's minimal Server; its Web page shows device status only.

Screenshots

Desktop

The current computer starts with Allow control of this device enabled and is available as a Host. Remote terminal access is also enabled by default and can be turned off in the Host's detailed Remote settings.

On another computer, select an online Host and open one of its workspaces.

The workspace opens in the native Harness interface, with the active Host and encrypted connection status shown in the header.

Android

Use text or image prompts, switch models, and access supported workspace files and terminals. The interface follows the system language and supports English, Simplified and Traditional Chinese, Japanese, Spanish, German, and French. In language settings, tap “More ...” to show all languages. See the Android guide for details.

The Bot button to the left of + on the Host workspace header opens the native DS Bot team mode: Bots, group chats, management, questions and interactive cards. In Bot mode, the header shows a Workspace switch immediately left of the three-dot menu. DS Bot must be enabled on the connected Host; see the Bot mode guide for availability and validation limits.

Mobile Settings includes an opt-in Compact conversations switch, applied globally when a conversation is next opened. Supporting Hosts send shorter historical tool details while preserving messages and tool status. Older Hosts keep the existing behavior. Turn it off and reopen the conversation to load full history.

How it works

DSH Desktop / Remote Web / Android
  ↔ authenticated, end-to-end encrypted channel
Remote Plugin on the Host
  ↔ supported Harness or optional Codex workspace support
Harness sessions/workspaces or Codex projects

The Harness Host does not need a public listening port. You can connect from anywhere with internet access.

Remote communicates over a bidirectional end-to-end encrypted channel and switches the client to the selected Host's native Harness API.

The original workspace, tools, and permission flow remain on that computer.

Every settings namespace currently registered by the Host can also be configured remotely through the official Harness settings API.

Credential values remain write-only, and Host-local document/open actions are never exposed.

Experimental ACP workspaces

The Host runs local AI backends and forwards prompts, streamed replies and approvals through the encrypted Remote channel.

Desktop and Android project their workspaces and sessions into the existing interface in memory, without writing them to Harness storage.

Supported backends:

• Cursor — connected through the CLI's ACP interface.
• Antigravity (AGY) — its stream-json CLI is adapted to the ACP gateway.
• Pi Agent (experimental) — install @earendil-works/pi-coding-agent and pi-acp on the Host, configure Pi's provider locally; Remote automatically detects and initializes Pi unless explicitly disabled in Remote settings. The workspace is available only after ACP initialization succeeds. Uses the separate ACP data plane. Tools run with Host-user permissions; per-tool confirmation requires a Pi extension and is not enabled by default.
• OpenCode — connected through opencode acp, with workspace discovery and history recovery. Host startup checks the CLI's supported options, accepting both native-listener and stdio-only ACP builds. Native session archiving on Desktop/Android requires the authenticated loopback API; builds without it report archiving unavailable. Archive state is saved by OpenCode; history is retained. Unarchive is not yet exposed.
• Claude — uses a locally authorized claude-agent-acp on the Host; enable it in Remote settings. Desktop/Android support workspaces, history, text prompts and approvals. Image input and direct Files/Terminal access are not available.

Model selection is available for Cursor, Claude, Pi, OpenCode, and AGY on Desktop/Android using the Host's actual model catalog and confirmed changes. Effort choices appear when advertised by the backend. Cursor uses a separate process per session so model changes cannot affect other conversations.

• Codex — connected through its independent App Server interface, with the same workspace entry.

Setup and adapter development: Agent workspace integration guide.

End-to-end encryption

Harness business traffic is encrypted on the Client and decrypted only by the selected Host using the fixed Noise_IK_25519_ChaChaPoly_SHA256 suite. Account membership and locally pinned device identity keys must both authorize a connection. The service can route connections and observe network metadata, but it cannot read session messages, prompts, tool output, workspace paths, or remote file contents. See End-to-end encryption for the handshake, key lifecycle, visible metadata, replay protection, and security limits.

Network and transport

The Host opens outbound connections only; it does not listen on a public port or require router port forwarding. Remote negotiates LAN -> P2P -> TURN -> Relay, falling back to the encrypted WebSocket Relay when WebRTC is unavailable or cannot connect. Every path carries the same Noise ciphertext and keeps the same Host/Client identity boundary. An established path that fails is closed and re-established on a new transport and Noise channel. A CONNECTION_FAILED error can come from the Server or from the Host's local fallback, so check the closedBy and retryable log fields before blaming WebRTC. See Network and transport for the topology, control and data planes, NAT behavior, fallback, reconnect semantics, and current validation status.

Creating a Harness workspace can create missing directories as the Host user, independently of the terminal switch. Paths must be absolute and non-root; created directories remain if registration fails.

OAuth sign-in methods are loaded from the Server. Use ds-harness-remote login list or /remote login list to see available QR providers; new server integrations need no further plugin release.

Security

• Session traffic is end-to-end encrypted. The service relays ciphertext without storing session plaintext or device private keys.
• Server membership and the Host's locally pinned peer identity must both authorize a connection.
• Interactive terminals use the Host-local terminal.enabled switch (on by default). They run as the Host user, independently of Agent approvals. General tool RPC and remote desktop remain unavailable.
• The workspace picker lists folders only and returns bounded, read-only directory metadata.
• Remote file preview cannot write, delete, upload, execute, or open a path in an external application.
• Codex Remote / Agent ACP is optional, can be disabled, and follows the same encrypted Host permission boundary as the rest of Remote.
• Removing a device revokes its credentials, membership, and active Remote connections.

FAQ

Do I need a public IP or port forwarding?

No. The Host only opens outbound connections and never listens on a public port.

Can the service read my conversations?

No. The service relays ciphertext only. Routing, authorization, presence and rate limiting require control metadata such as account and device ownership, online status, connection times and connectionId; prompts, conversation content, tool input and output, workspace paths and file preview contents stay unreadable.

Which machine can act as a Host?