DeepSeek Harness Remote Connection for NanoAI
ds-harness-remote provides authorized devices access to permitted DeepSeek Harness sessions and workspaces through NanoAI. Host execution and permission checks remain on the Host.
Install and configure
- Install and enable DeepSeek Harness Remote Connection directly in the DSH profile. No separate NanoAI Plugin Market installation is needed first; follow any restart prompt.
- The same profile must provide
@deepseek-ai/dsh-credentials and a compatible official Harness Remote carrier. Configure the service origin and API Key in Remote's NanoAI connection settings. Remote and NanoAI Plugin Manager use their own credential records by default; the manager is optional for independent Remote use. The Key needs remote:connect permission and the deployment must enable Remote access.
- Open DeepSeek Harness Remote Connection and explicitly allow the local computer to act as a Host. There is no separate Remote password, GitHub/Zhihu QR login or registration-code login.
- Open DeepSeek Harness Remote Connection on the same NanoAI platform, select an authorized online Host and open a workspace. The platform browser flow registers its client and acquires connection credentials automatically.
Each plugin offers an explicit checkbox to reuse the other plugin's service origin and API Key in the same profile. Its own original configuration is retained and used again when reuse is disabled. Only one side may reuse the other: mutual reuse is rejected, and conflicting stored configuration fails closed. Each operation reads the peer record afresh to observe rotation. A shared Key must have remote:connect and the manager's catalog/download permissions for the operations used.
Correct missing, invalid, expired or revoked credentials at the selected source. The stored API Key is never returned to the frontend. Same-origin changes apply to Remote's next request; reload Remote after its effective service origin changes and provide a matching Key. Server relay service-account passwords must never be configured as client credentials.
Personal access and sharing
Devices are personal and private by default. A Host owner can explicitly share access with named recipients. Workspace membership, billing ownership and operational administrator roles do not grant access to another person's sessions. Device-information permission does not grant control. Discovery, connection issuance and ongoing access enforce authorization and revocation.
The Host must allow control locally. Host-local terminal access runs as the Host user and follows the terminal setting. File previews remain bounded and read-only. Noise identity verification and transport encryption remain part of the connection boundary; the Host opens outbound connections without a public listening port.
Scope and troubleshooting
A missing Remote API indicates that the selected profile lacks a compatible official Harness carrier; configure the matching runtime components. An offline Host requires checking the Remote origin/Key, platform authorization and local Host access settings. Keep the Host running while connecting.
The Node relay remains active behind the NanoAI Go gateway, which owns NanoAI authorization and personal sharing. Its service-account password authentication is server-side infrastructure. Platform setup, gateway routing and live verification belong to the deployment operator.
Codex, Cursor and Antigravity adapters remain optional experimental upstream capabilities. The Android app source and its build/release paths have been removed; no iOS app source was maintained here. Browser-extension and VS Code sources remain upstream references, not validated NanoAI products. Upstream hosted services and mobile beta paths are not supported NanoAI user paths. TUI users reuse the same Remote connection settings and compatible carrier; QR login is retired. TUI compatibility requires validation in the target profile.
Web compatibility
Remote 0.5.36 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.36 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. Package names and protocol identifiers are retained for compatibility. Existing upstream authorship and copyright remain intact. Licensed under the MIT License, copyright 2026 DSH Remote contributors. This independent community project is not an official DeepSeek product; trademarks belong to their respective owners.