DeepSeek Harness Plugin Hub

发布与管理完整 Harness Profiles,发现适合你的插件。

探索

插件目录环境预设文档中心动态

社区

发布插件联系我们报告问题

相关链接

Plugin Hub GitHubDeepSeek Harness 官方项目系统状态隐私说明
© 2026 DeepSeek Harness Plugin HubPowered byPaxTech

独立、非官方社区项目,与 DeepSeek 官方无隶属、授权或背书关系。

Plugin Remote — DeepSeek Harness 插件(DSH Plugin)
DeepSeek Harness Plugin Hub
ProfilesPlugins分类动态文档登录管理 Profiles
ProfilesPlugins分类动态文档登录
← Plugins
P

dsh-plugin-remote

Plugin Remote

DeepSeek Harness Web GUI 的远程访问网关和免安装 Windows 桌面投影

插件会安装到这里;不确定时保持 web。

npx -y @deepseek-ai/dsh plugin --profile web add dsh-plugin-remote@0.5.12
README兼容性版本

说明

DeepSeek Harness Web GUI 的远程访问网关和免安装 Windows 桌面投影。

兼容性与来源证明

Plugin Remote 以 dsh-plugin-remote 发布,当前版本为 0.5.12。Plugin Hub 会校验它的 manifest,并保存精确安装来源,便于复现安装结果。

DSH 兼容范围
*
运行环境
web
发布来源
npm
Registry 更新时间
2026/8/21

版本

0.5.12stable
2026/8/21

相关插件

正在加载相关插件…

最新版
0.5.12
DSH
*
HMR
重启进程
Tree shaking
未声明可安全裁剪
解包体积
993 kB
文件数
35
Surface
web
许可证
MIT
发布源
npm
GitHub
★ 0
周下载
0
最近提交
2026/8/21
查看源码 ↗
README Badge

点击下方 Badge 复制 Markdown,粘贴到 README 即可。

这是你的 Plugin?认领权益 · 优先安全扫描

验证 package.json 声明的 GitHub 仓库,即可管理这个公开页面。认领后,Hub 会优先安排当前版本的安全扫描,并在通过后公开展示结果。

认领这个 Plugin →
报告问题

相关插件

继续浏览 productivity-workflow 分类下经过校验的插件。

Acp App@deepseek-ai/dsh-acp-appdsh ACP 配置文件包:基于 dsh-base 的仅限自动化的 JSON-RPC stdio 和进程生命周期管理Client Ui Task Board@linxin666/dsh-client-ui-task-board面向 DSH Web GUI 的主机权威任务面板,支持实际会话执行、主机 cron 调度以及可选的跨平台空闲睡眠保护;以挂载方式提供,无需修改 DSH 源代码。Web All@linxin666/dsh-web-allDSH Web UI 全家桶聚合插件:一键安装全部功能插件(task-board / git-graph / pet / remote-web-ui / web-ui-settings / skin-center / community-plugins / compat shim)。compat 桥接层已并入本包(src/client),无需独立 compat npm 包。Agent Teams@nanmicoder/dsh-agent-teamsAgentTeams for DeepSeek Harness:通过自然语言驱动多智能体团队协作(队长、成员、具有依赖关系的任务、消息传递),并在 Web GUI 中提供树状监视器

README

dsh-plugin-remote

Remote access gateway for the DeepSeek Harness (DSH) Web GUI — login auth + HTTP/WebSocket reverse proxy to the loopback DSH server.

中文 · MIT

Install

dsh plugin --profile web add dsh-plugin-remote && dsh web

Note: this is a DSH (DeepSeek Harness) plugin — install it into a profile through dsh plugin (or the profile's dependencies) so the gateway activates; a plain npm i alone does not wire it in.

Screenshots

LoginMain view (对话 / 轨迹 / 远程访问 tabs)
loginmain view
Remote desktop tabSettings → Remote Access
remote desktopsettings

Features

  • Login-gated remote access: scrypt credentials + HttpOnly session cookie; HTTP/WebSocket reverse proxy with Host/Origin rewriting — no --trusted-host needed
  • White-themed login page (shadcn/ui, mobile-friendly) with the DeepSeek Harness brand
  • Gateway admin API (/admin/*, session-required), managed in the Settings → 远程访问 section:
    • Remote-access whitelist (IP / CIDR; loopback always allowed; hot-reloaded)
    • Account password changes (old sessions revoked immediately)
    • Request log: every request persisted to per-day JSONL shards, download + 1/3/7-day retention rules
  • Localized zh/en, follows the GUI language
  • Zero-install Windows desktop projection: the plugin starts its bundled x64 native helper automatically; no .NET, FFmpeg, driver, or separate agent installation is required
  • Interactive remote desktop as a dedicated 远程访问 tab in the conversation view ring (next to 对话/轨迹), projecting the Windows desktop full-width with pointer input, keyboard input, and weak-network/balanced/sharp quality profiles. The primary WAN transport is WebRTC with independent lossy frame/pointer channels and a reliable control channel; the original WebSocket viewer remains an automatic fallback
  • The gateway keeps its custom HTTP/WebSocket plumbing on Node built-ins; the optional native node-datachannel package provides the WebRTC fast path and the Next.js login app lives inside gateway/

Usage

  • Open http://<server-ip>:4080 — the first visit creates the only account
  • Manage accounts: node lib/remote-passwd.mjs add|set-password|list|del <username>
  • Data lives under $DSH_HOME/plugin-data/dsh-plugin-remote/ (users.json, whitelist.json, logs/)

Windows desktop

On Windows 10/11 x64, the plugin launches native/windows-x64/dsh-remote-host.exe after the gateway becomes ready. It connects back with a random process-local authentication token that is never written to disk. Only logged-in gateway users can open the viewer/control channel.

The current Windows helper source has two video paths. After native:build, the primary path captures BGRA frames, encodes H.264 through Media Foundation, and sends one access unit into a real WebRTC H.264/RTP track. The browser and libdatachannel then use the media transport's pacing, congestion feedback, NACKs, and keyframe requests instead of putting every full frame into a TCP queue. During startup or when H.264 cannot be decoded, the gateway keeps the JPEG DataChannel path alive and switches to it automatically; the authenticated WebSocket viewer is the final compatibility fallback. The package prefers the dsh-remote-host-h264.exe binary when present and keeps the old exe as a legacy fallback; npm run native:build refreshes both copies.

Pointer motion and wheel events use a disposable low-latency channel, while keyboard, button transitions, ACKs, and input-reset messages remain ordered and reliable. This prevents stale video from blocking new input on a weak link.

For clients behind symmetric NAT or UDP-restricted networks, configure a TURN server in the plugin row. The values use the browser RTCConfiguration shape:

{
  rtcIceServers: [
    'stun:stun.example.net:3478',
    { urls: 'turns:turn.example.net:5349', username: 'user', credential: 'secret' },
  ],
}

STUN is useful for direct paths; TURN is the reliable relay fallback. Keep the WebSocket fallback enabled when deploying in environments where UDP policy is unknown.

Windows secure desktops (UAC prompts, sign-in, and locked sessions) cannot be captured or controlled. Set config.desktop: false to disable projection.

Development verification

npm run native:build
npm run gateway:build
npm run test:desktop

License

MIT