frozo-ai/dsh-worlds

Name: frozo-ai/dsh-worlds
Author: frozo-ai

Plugin插件 Native原生 ⭐ 3 Approval & Security审批与安全 Notifications & Remote通知与远程 Dev Workflow开发与代码工作流

DeepSeek Harness的远程执行环境：在容器内运行代理的Bash、终端、LSP和文件工具。零依赖。

Project Overview项目介绍

Edited by Zhiwei Agent (zhiwei)由知微Agent(zhiwei)编辑

This is a native plugin built exclusively for DeepSeek Harness (DSH) that addresses DSH's native limitation where execution state is not retained after a harness restart. It moves the entire agent execution environment into a Docker container, so all state including working directory, exported environment variables, and running background processes persists across DSH process restarts. To install the plugin, you first need to have Docker installed and a built copy of DSH on your local machine. Then you clone the repository, run the built-in test suites to verify functionality, and add it to your DSH profile via the DSH plugin command.

After installation, the plugin works automatically with existing DSH plugins like dsh-bash-local, dsh-terminal-bash, and dsh-lsp-stdio without any forking or modification. It automatically redirects all file system and sub-process operations to the container, so existing tools work out of the box with the persistent environment. A common workflow is to create state and start a long-running background process in one DSH process, exit DSH, then reconnect to the same container environment with a new DSH process, finding all state intact. This plugin is ideal for DSH developers who work on long-running tasks that need to survive harness restarts without losing any work progress.

This plugin has zero npm dependencies, and relies only on Node.js built-in modules including node:http, node:net, and node:crypto. There are several documented limitations users should be aware of before use: it does not support ongoing piped stdin input, container-level security is coarser than DSH's native per-call sandbox, and blocked tty reads are detected via heuristic only. The container image requires bash, ps, and base64 pre-installed, the plugin will automatically attempt to install missing tools, and the project is released under the open source MIT license, and is not affiliated with DeepSeek AI.

这是一个专为 DeepSeek Harness（DSH）开发的原生插件，用于解决 DSH 重启后代理执行环境无法保留的问题。它将整个执行环境迁移到 Docker 容器中，让工作目录、环境变量、后台进程等状态都能在 Harness 进程重启后保留，无需重新搭建开发环境，让开发流程更顺畅。

你需要提前安装好 Docker 环境，然后通过 DSH 的插件管理命令将该插件添加到配置文件中，即可正常使用。你可以先在第一个 Harness 进程中创建状态、启动后台进程，退出后再用新的 Harness 进程接入同一个容器环境，所有之前的开发状态都能完整保留下来。

该插件没有额外的 npm 依赖，仅使用 Node.js 内置模块即可运行。它存在一些已知限制，比如不支持管道模式的持续 stdin 输入，容器边界比细粒度沙箱更粗糙，使用前需要了解这些限制。项目采用 MIT 许可证开源，不隶属于 DeepSeek AI。

View on GitHub在 GitHub 查看

Send to your DSH发给你的 DSH 安装

请帮我安装这个 DSH 插件。安装前先完成【兼容性检查 + 安全性检查】，检查通过再动手。

插件：dsh-worlds（frozo-ai/dsh-worlds）
仓库：https://github.com/frozo-ai/dsh-worlds
本站详情页：https://www.yhbd.top/plugins/frozo-ai-dsh-worlds/
本站登记：类型 plugin · 归类 原生 DSH 插件 · 许可证未声明 · ⭐ 3 · 最近提交 2026-08-18 · 主语言 JavaScript

按下面顺序执行，每步先把结论告诉我，再进入下一步：

【1 兼容性检查】
① 我这边：DSH 版本、Node 版本、操作系统、当前 profile（web / desktop）。
② 读它的 README、package.json、插件 manifest，列出它要求的 DSH 版本 / Node 版本 / 操作系统 / 外部依赖 / 需要另外先装的运行时。
③ 逐条比对，结论只写「满足 / 不满足 / 未知」三种；不满足的给出可行替代方案。
④ 检查是否和我已装的插件冲突：命令名重复、skill / tool 重名、端口占用、重复注册的 MCP server。

【2 安全性检查】
① 仓库可信度：和上面「本站登记」是否一致；star / fork 数、创建时间、最近提交，是否归档或长期停更。
② 安装脚本：逐行看 package.json 的 preinstall / install / postinstall，以及 install.sh、setup.ps1 之类脚本。出现 curl|bash、下载后直接执行、混淆代码、访问与插件功能无关的域名，立刻停下来告诉我，不要继续装。
③ 依赖：列出新增依赖，标出无人维护、或与知名包拼写近似的可疑包（typosquatting）。
④ 权限与副作用：它会读写哪些目录、访问哪些域名、需要哪些 DSH 权限（filesystem / network / shell / clipboard 等），以及怎么卸载和回滚。
⑤ 如果它要求 sudo / 管理员权限，或权限明显超出功能所需，先停下来问我。

【3 安装】
上面两步没有「不满足」和「高危项」时才执行；用官方推荐方式安装，不要自行提权。

【4 汇报】
用表格输出：检查项 / 结论 / 依据 / 是否需要我决策。拿不准的一律写「未知」并说明要我怎么确认——不要猜，也不要替我决定。

Send this message to DSH in your current session: it verifies compatibility and security first (answering met / not met / unknown item by item) and only installs once everything checks out — it will stop and ask you if it finds a high-risk item. The box scrolls; the copy is the full prompt. CLI install commands may not be accurate across systems, so DSH is the safer route.把上面这条消息直接发给当前会话里的 DSH：它会先核对兼容性与安全性（逐条给「满足 / 不满足 / 未知」），确认没问题再安装，有高危项会停下来问你。框内可滚动，复制到的是完整提示词；安装命令不一定准确，发给 DSH 更稳。

Pre-install check安装前体检Compatibility · Security兼容性 · 安全性 2 warnings2 项注意

No license declared - all rights reserved by default; ask the author before commercial use or redistribution未声明开源许可证 —— 默认「保留所有权利」，商用或再分发前先问作者
Only 3 stars - very few users, little community feedback星标只有 3，几乎没人在用，遇到问题缺少社区反馈

DSH walks through these 9 checksDSH 会逐条核对这 9 项

Compatibility兼容性

DSH, Node, OS and profile requirementsDSH 版本 / Node 版本 / 操作系统 / profile 是否满足要求
External dependencies and runtimes (Electron / Python / Docker, ...)外部依赖与运行时（Electron / Python / Docker 等）是否齐备
Conflicts with installed plugins: command names, skill / tool names, ports, duplicate MCP registration与已装插件是否冲突：命令名、skill / tool 重名、端口占用、重复 MCP 注册

Security安全性

Repo matches the facts registered here; archived or abandoned?仓库是否与页面登记一致，是否归档或长期停更
Safety of preinstall / install / postinstall and install.sh / setup.ps1preinstall / install / postinstall 与 install.sh、setup.ps1 是否安全
curl|bash, download-then-execute, obfuscation, unrelated domains → stop immediatelycurl|bash、下载即执行、混淆代码、无关域名 → 立刻停止
Typosquatting or unmaintained packages among the new dependencies新增依赖里有没有 typosquatting 或无人维护的包
Requested permissions vs. what the feature actually needs申请了哪些权限、是否超出功能所需（filesystem / network / shell / clipboard）
Any sudo / admin requirement, plus uninstall and rollback是否要求 sudo / 管理员权限，以及卸载与回滚方式

Anything uncertain must be marked unknown with a note on how to confirm it. This site's signal screen is a static snapshot, not a security audit.拿不准的必须标「未知」并说明要我怎么确认。本站的信号筛查是静态快照，不能替代安全审计。

Or use CLI install (for developers)或使用命令行安装（适合开发者）

CLI Install命令行安装

dsh plugin --profile headless add github:frozo-ai/dsh-worlds

把 frozo-ai/dsh-worlds 加入你的 DSH 配置（web profile）即可启用。

READMEREADME

4.2 KB · 缓存于 2026-08-29 05:30:45 · 4.2 KB

dsh-worlds

Run the agent's execution world inside a container — so it survives the harness that started it.

DeepSeek Harness records this limitation in packages/terminal/terminal/README.md:

"Sessions are process-local and are not restored after a harness restart."

The session log is durable. The computer the agent was working on is not — the shell dies with the harness, taking your cwd, exported variables, and background processes with it.

dsh-worlds fixes that by moving the execution world into a Docker container. No CRIU, no microVMs: a container simply outlives its client.

harness process A            harness process B (a different process)
      |                                    |
      +------> [ container: dsh-world ] <--+
                cwd · env · running procs

Why two plugins move everything

From the harness's own architecture docs:

"The existing dsh-bash-local, dsh-terminal-bash, and dsh-lsp-stdio need no forks. They delegate every execution-world operation to ctx.fs and ctx.subprocess."

Implement those two seams and Bash, persistent PTY terminals, LSP, and every file tool relocate into the container automatically. That is a deliberate architectural gift, and this project is what happens when you take it.

Status

Capability	Checks
Docker Engine API client + stream demux	11 unit + 12 live
`ctx.fs` — all 12 methods	38 live
Bounded collect buffers (offset-based, non-consuming)	11 unit
`ctx.subprocess` — spawn, tree termination, `waitForExit`	22 live
PTY — `spawnTerminal`, resize, foreground signalling	17 live
Total	111

Zero npm dependencies. node:http, node:net, node:crypto only.

Try it

Requires Docker and a dsh checkout that has been built.

git clone https://github.com/frozo-ai/dsh-worlds
cd dsh-worlds
npm test              # unit suites, no Docker needed
npm run verify        # live: Docker client
npm run verify:fs     # live: filesystem provider
npm run verify:subprocess
npm run verify:terminal

Then install it into a dsh profile — it ships a dsh.bundle manifest, so it mounts by package name with no path editing:

Showing the opening section of the README — the full document lives in the repository以上为 README 开头摘要，完整文档在仓库内 · View the full README on GitHub →在 GitHub 查看完整 README →

渲染基于仓库 frozo-ai/dsh-worlds 的 README.md。在 GitHub 查看原文 →