DeepSeek Harness Plugin Hub

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

探索

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

社区

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

相关链接

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

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

DeepSeek Harness Plugin Hub
ProfilesPlugins分类动态文档登录管理 Profiles
ProfilesPlugins分类动态文档登录
← Plugins
P

@citisen/dsh-plugin-dev

Plugin Dev

用于 DeepSeek Harness 插件的开发工具包:编写配置文件、启动一次性影子环境、验证主机端、捕获客户端端,并回滚损坏的配置文件——由随附的代理技能驱动

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

npx -y @deepseek-ai/dsh plugin --profile web add github:caparisen/dsh-plugin-dev#cf41a969f83992c45764e47e7eb97ee084f1c280
README兼容性版本

兼容性与来源证明

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

DSH 兼容范围
*
运行环境
any
发布来源
github
Registry 更新时间
2026/10/20

版本

0.1.0stable
2026/10/20

相关插件

正在加载相关插件…

最新版
0.1.0
DSH
*
HMR
重启进程
Tree shaking
未声明可安全裁剪
解包体积
未提供
文件数
未提供
Surface
any
许可证
MIT
发布源
github
GitHub
★ 0
周下载
0
最近提交
2026/10/20
查看源码 ↗
README Badge

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

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

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

认领这个 Plugin →
报告问题

相关插件

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

Web App@deepseek-ai/dsh-web-appdsh 浏览器界面捆绑包:位于 dsh-base 之上的 Web 补丁层,加上运行时粘合插件(提供前端 dist、Web 界面提示符、bash 运行时变量和 URL 行)Sdk Minimal@deepseek-ai/dsh-sdk-minimal独立的最小 SDK 配置包:JSON-RPC、一个 DeepSeek 适配器、持久化 Shell 和 JSONL 会话Sdk App@deepseek-ai/dsh-sdk-appdsh SDK 配置包:基于 dsh-base 提供 stdio JSON-RPC 服务和进程生命周期管理Experimental Inspector@deepseek-ai/dsh-experimental-inspector用于 Host 调试和 Client Runtime 检查的实验性跨 realm CDP hub

README

@citisen/dsh-plugin-dev

Development kit for DeepSeek Harness (dsh) plugins: a small CLI for the parts that must be deterministic, and a bundled agent skill for the judgment in between.

Most dsh plugin failures are not code failures. They are composition failures (a row that does not resolve, a patch that replaces a whole config, a provider id that collides) or client half failures (a bundle that never mounts). None of those show up in a unit test, and all of them cost an afternoon when the only feedback is a broken app.

dsh-plugin-dev doctor                              # what this machine can test
dsh-plugin-dev compose --profile desktop --json    # the tree the launcher would mount
dsh-plugin-dev shadow  --from desktop --hold       # boot a throwaway copy, print url + token
dsh-plugin-dev shot    --url "$URL" --out shot.png # render it, capture console errors
dsh-plugin-dev snapshot save --profile desktop     # something to go back to

Why a package and not a script

dsh is an order of magnitude easier to develop against when the loop is: compose → diff → boot → look. That loop is four commands, and each of them is fiddly in a way that should be solved once:

  • the desktop profile is refused by the CLI ("managed exclusively by the Electron application"), so every check needs a copy;
  • the GUI answers 401 without its token, and readiness is a 303 token exchange, not a 200;
  • chrome --headless --screenshot hangs forever on the SPA;
  • a link: dependency that a package manager replaces can delete the linked worktree, .git included.

The commands encode those; the skill explains when to use which, and why.

Install

As a bundle, so the agent gets the skill (recommended):

dsh plugin --profile desktop add @citisen/dsh-plugin-dev

The package registers a skill provider, so dsh-plugin-dev appears in the agent catalog. No other profile row is touched, and disabling the bundle removes it again.

Standalone, for the CLI without the skill:

npx @citisen/dsh-plugin-dev doctor
# or
npm i -g @citisen/dsh-plugin-dev

Commands

CommandWhat it does
doctorDetects the launcher and its version, lists profiles, checks whether the chosen profile composes, finds a Chromium
composeComposes a profile through the real launcher. --save records a baseline, --check exits 1 on drift, --json lists entries and duplicate ids
shadowCopies a profile (files copied, node_modules linked), boots it on an OS-assigned port, waits for the URL, probes it, prints url/token/log
shotRenders a URL in headless Chromium over CDP: PNG, DOM stats, console errors and uncaught exceptions. --fail-on-console-error makes them fatal
snapshotSaves, lists and restores the three files that decide a profile's composition. restore snapshots the current state first

Common flags: --dsh <path>, --json, --help.

Requirements

  • dsh — the desktop application (the bundled CLI is found automatically), the published CLI on PATH, or --dsh <path> / $DSH_CLI.
  • Node 20+ for the CLI.
  • Chromium, Chrome or Edge for shot (found automatically; --browser <path> or CHROME_PATH otherwise).
  • Windows, macOS and Linux. The desktop app is optional: any dsh works.

How it works

Nothing is reimplemented. compose runs dsh --profile <p> --dump-config and diffs that text; shadow runs dsh --profile <copy> --no-open --port 0 and reads the URL the launcher prints; shot drives the browser over the DevTools protocol and nothing else. When the launcher refuses the desktop profile, compose and shadow build a temporary copy under another name — the same workaround a person would do by hand.

The host half is deliberately trivial: it reads skills/dsh-plugin-dev/SKILL.md and registers one skill provider. It cannot fail a profile boot.

Version support

Tested with dsh 0.2.1-rc.2 on Windows 11 (Electron 44 / Node 24.21). The kit shells out to the launcher, so a version that changes --dump-config, the dsh web: boot line, or the desktop-profile policy will surface as a loud error from doctor rather than a silent wrong answer. Please open an issue with the doctor --json output.

Contributing

The trap list is the product. See CONTRIBUTING.md — the short version is: a step becomes a script on its second manual repetition, and a bug report becomes an entry in skills/dsh-plugin-dev/references/traps.md.

License

MIT