ds-harness-remote

English  ·  中文  ·  Documentation  ·  Download: Windows  ·  macOS  ·  Linux  ·  Web  ·  Android

npm  ·  GitHub  · 

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. Remote is simply another window into that environment.

Features

• Continue active sessions and review their latest progress from another device
• Send new instructions, change direction, and use image prompts with Harness dsh-v0.1.1-rc.2 or dsh-v0.1.2-alpha.1–alpha.2
• Answer questions and permission requests from clients with live conversation controls
• Open workspaces from another authorized computer on the same account
• Reuse the native Harness interface instead of maintaining a separate desktop conversation UI
• Preview remote files between two Harness installations with the optional dsh-file-viewer plugin
• The Harness Host does not need a public listening port. Connect securely from anywhere with internet access over a bidirectional end-to-end encrypted channel

Install

Path A: DSH Desktop

Install DSH Desktop on Windows, macOS, or Linux. Remote is included and enabled by default, so no separate plugin installation is required.

Path B: Existing DSH installation

Install the exact npm version for the web profile:

dsh plugin --profile web add ds-harness-remote@0.4.2

Restart Harness after installation.

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. New password accounts can register through Remote Web; the site shows the current invitation requirements.
3. Enable remote control for the current computer.
4. On another device, open DSH Desktop, 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.

The public service currently uses the hosted Remote relay. A supported self-hosted relay option is not available yet.

Screenshots

Desktop

Enable Allow control of this device in Remote settings to make the current computer available as a Host.

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

Download the latest Android APK from GitHub Releases.

Sign in to the Android client with your existing account, select an available computer, open a workspace, and continue the conversation with text or image prompts.

How it works

DSH Desktop / Remote Web / Android
  ↔ authenticated, end-to-end encrypted channel
Remote Plugin on the Host
  ↔ allowlisted native Harness API
Harness sessions, tools, and workspaces

The Harness Host does not need a public listening port. You can connect from anywhere with internet access, and Remote communicates over a bidirectional end-to-end encrypted channel. It switches the client to the selected Host's native Harness API, so 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.

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 File Viewer content. 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. See Network and transport for the topology, control and data planes, NAT behavior, fallback, reconnect semantics, and current validation status.

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.
• Remote does not expose a direct shell, PTY, general tool RPC, or remote desktop. Harness tools may still modify files or run commands on the Host under Harness's normal permission controls.
• The workspace picker lists folders only and returns bounded, read-only directory metadata.
• Optional File Viewer access is limited to authenticated, encrypted range reads and continues to enforce provider root and locator authorization.
• Remote file preview cannot write, delete, upload, execute, or open a path in an external application.
• Removing a device revokes its credentials, membership, and active Remote connections.

Compatibility

Breaking change notice: Plugin 0.4.1 removes the earlier experimental Remote business RPC surface (sessions.*, session.*, permissions.respond, sync.from). Harness session traffic now only uses the official rc.2 ApiProxy or the alpha Typert Remote Gateway, and this plugin does not provide an adapter or wire-format translation for the old RPC surface.

Plugin 0.4.2 supports DeepSeek Harness dsh-v0.1.1-rc.2 through the legacy official ApiProxy, and dsh-v0.1.2-alpha.1–alpha.2 through the official Typert Remote Gateway. A 0.4.2 Client running rc.2 remains compatible with older rc.2 Hosts through the legacy capability fallback.

Both Desktop endpoints must use the same Harness transport generation. Plugin 0.4.x does not translate rc.2 and alpha business models: an alpha Client cannot open an rc.2 Host, and an rc.2 Client cannot open an alpha Host. Mixed connections are rejected before switching the native UI or mutating a Workspace.

Documentation

• Plugin guide
• Documentation index
• End-to-end encryption
• Network and transport
• Remote Protocol
• Development status and roadmap

Links

• Friendly link: LINUX DO
• Friendly link: Cyber Liu Kanshan

Project status and trademarks

This is an independent community project and is not an official DeepSeek product. DeepSeek and related names and marks belong to their respective owners.

License

MIT