DeepSeek Harness Remote Connection for NanoAI

中文 · Documentation

DeepSeek Harness Remote Connection connects authorized devices to a NanoAI-authorized DeepSeek Harness Host, letting them continue permitted sessions and workspaces; execution and permission checks stay on the Host.

Install and connect

1. Install and enable DeepSeek Harness Remote Connection directly in your DSH profile. No separate NanoAI Plugin Market installation is needed first; follow the runtime's restart prompt.
2. Open DeepSeek Harness Remote Connection's NanoAI connection settings and save the service origin and API key. Remote and NanoAI Plugin Manager each use their own @deepseek-ai/dsh-credentials record by default. The manager is optional for independent Remote use. The Key must have remote:connect permission.
3. Open DeepSeek Harness Remote Connection and explicitly allow this computer to act as a Host. The profile must include a compatible official Harness Remote carrier and the deployment must enable Remote access. No separate Remote password, QR login or registration code is required.
4. In the same NanoAI platform, open DeepSeek Harness Remote Connection, select an authorized online Host and open a workspace. The platform browser flow registers its client and obtains connection credentials automatically.

Each plugin offers an explicit checkbox to reuse the other plugin's service origin and API Key in the same profile. Reuse preserves its own original configuration, which is used again when reuse is disabled. Only one plugin may reuse the other at a time: enabling mutual reuse is rejected, and any conflicting stored configuration fails closed. Each operation reads the selected peer record afresh so key rotation is observed; missing, invalid, expired or revoked credentials must be corrected at the selected source. A shared Key needs remote:connect and the manager's catalog/download permissions for the operations used.

Update the service origin and Key at the selected credential source. Changing Remote's effective origin requires a matching Key and reloading Remote; same-origin changes apply to the next request. The stored API Key is never returned to the frontend. Relay service-account credentials belong only on the server.

Devices are personal and private by default. Owners can explicitly share a Host with named recipients. Workspace membership, billing ownership and operational administrator roles do not grant access to another person's sessions. Viewing device information does not grant control; the platform checks discovery, connection and continued access, including revocation.

Capabilities and boundaries

• Continue Host workspaces and sessions through the Harness Remote carrier and an encrypted channel.
• Use the supported workspace file tree, bounded read-only previews, Host-local terminals and authorized development-service previews. Terminal access follows the Host-local setting and runs as the Host user.
• Keep device identity keys on the endpoints; preserve the upstream Noise protocol and transport implementation. The Host opens outbound connections without requiring a public listening port.
• Optional Codex, Cursor and Antigravity adapters remain experimental upstream capabilities; availability depends on Host configuration and a matching carrier.

The Node relay in apps/server remains active behind the NanoAI Go gateway. Its service-account password authentication is server-side infrastructure. The gateway owns NanoAI user authorization and personal sharing. Route public access through that gateway; see Remote deployment and operations and platform deployment.

The Android client was removed from this repository on 2026-10-17; no iOS app source was present, and the iOS beta link has been removed. Browser-extension and VS Code directories remain upstream references, not validated NanoAI products. Historical mobile releases are not installation or connection paths for this fork. The documentation index separates current instructions from upstream technical references.

Build from source

Use Node.js 24.20.0 and the pinned pnpm@12.9.1. From this directory:

pnpm install --frozen-lockfile
pnpm --filter @dsh-remote/protocol --filter @dsh-remote/crypto --filter @dsh-remote/webrtc --filter @dsh-remote/client-core build
pnpm --filter ./packages/plugin check
pnpm --filter ./packages/plugin build

These commands build the plugin and shared packages; they do not deploy the platform, publish a package or validate a live NanoAI connection. Installation details explain profile and credential requirements. Relay packaging and platform verification follow the deployment guides above.

Web compatibility

Remote 0.5.34 loads the official Web interface from the running Host, keeping its sidebar, sessions and modules on the same Harness version. Update the Host plugin to 0.5.34 and reload the NanoAI page. The Host profile must provide the official Web server and compatible Harness Remote carrier. A newer Host can require corresponding Remote support; declaring a peer range does not establish compatibility with every future Harness release.

Use HTTPS for public NanoAI services. HTTP is supported for localhost and literal private, link-local or carrier-grade NAT IPv4 addresses; credentials sent to an HTTP service are not protected by TLS.

Origin and license

Derived from the upstream project liguobao/ds-harness-remote, with NanoAI integration maintained in this repository. Existing upstream authorship, copyright and protocol identifiers are retained. Licensed under MIT, copyright 2026 DSH Remote contributors.

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