dsh-kit

这是我的 DeepSeek Harness 插件套装，也是我日常在用的一套。

我把它们整理成了一个可以直接安装的仓库：你在自己的 Harness 上跑一条命令，就能装上我配置的这些插件和版本。想改什么，fork 我这个仓库自己维护，或者只装其中几个。

> 找更多 Harness 插件？GitHub 上搜 dsh-plugin 话题。

English

这里有什么

我自己写的这几个（源码在这个仓库里）：

我改过的这些（上游在 npm，我改的地方源码也放进来了，装的是我这份）：

别人做的这些（从 npm 装，清单里锁了版本，我没把源码再拷一份）：

dsh-context、@modusensus/dsh-mneme（长期记忆）、dsh-better-sidebar、@changfenhuang/dsh-genui（界面组件）、@goodandready/* 两个（dsh-context-lens、dsh-time-machine）、@linxin666/* 三个（session-archive、usage、client-ui-model-capabilities）、billion-context、dsh-claude-style、dsh-super-code、ds-bot、dsh-github-connect、@tt-a1i/archify-dsh、@deepseek-ai/dsh-subagent-claude-code、@michengai/dsh-skills-manager。

完整清单和版本在 manifest.json。

本机开着、但不归这个库管的两个：kaoyan-workbench（自己的仓库 Aceared0829/kaoyan-workbench，用 link: 挂进 profile）、@local/dsh-turn-autocontinue（只在 default-workspace/bundles/ 里的本地 bundle，没有单独仓库）。这两个不在清单里，安装器不会去动它们。

Harness 自带、默认关着的实验包，我这套里也开了：agent team、语音输入、自动评审、inspector、worktree 工具、CoT 翻译、终端、会话搜索、会话标题、badge skill、ralph、插件市场、个性化推荐。装的时候会自动检查你那边有没有这些包，没有就跳过，不会为了装上而改你的 Harness。

装到你的机器上

前提：你已经装好 DeepSeek Harness，dsh 能在终端里跑。这个仓库不装 Harness 本身。

Desktop 用户注意：先在应用里注册「管理 dsh 命令」，然后从托盘完全退出。只关窗口不够——Host 还在后台跑的时候装不了 desktop profile。

git clone https://github.com/Aceared0829/dsh-kit.git
cd dsh-kit
.\install.ps1

macOS / Linux：

git clone https://github.com/Aceared0829/dsh-kit.git
cd dsh-kit
chmod +x install.sh
./install.sh --profile web

装完重新打开 Harness。

常用参数：

• -Profile desktop / --profile desktop：装进 Desktop 的 profile。没找到 Desktop 自带的 dsh 会拒绝，免得用普通 CLI 把 desktop profile 改坏
• -Profile web：装进 Web / 终端 profile
• -DryRun：只打印要跑的命令，不动 profile。想先看看会改什么就用这个
• -SkipPreferences：不套用我的设置模板
• -Home：指定 Harness home。默认用 DSH_HOME，再没有就是 ~/.dsh

安装器会往你的 profile 里补几个 pnpm 设置

第一次装的时候，安装器会往 profile 的 pnpm-workspace.yaml 里补几项，不然装不上：

• allowBuilds：放行 Harness 运行时的原生包（node-pty、koffi、protobufjs、@deepseek-ai/dsh-subprocess-local、@google/genai），外加 ssh2、cpu-features——这两个是装 dsh-ssh 这类插件时才会用到的，先放行省得你之后自己加插件又被 pnpm 拦住。pnpm 11 只要见到没批准的构建脚本就整次中止
• nodeLinker: hoisted 和 autoInstallPeers: false：跟 Harness 自己的 profile 布局保持一致

只补你没有的。已经在用的 profile 不会被重写，改之前会备份成 pnpm-workspace.yaml.bak-dsh-kit。

想自己维护

fork 这个仓库，或者直接改你 clone 下来的那份。

改插件源码：plugins/ 下面就是。装的时候是 link: 到 clone 的目录，所以改完 git pull（别人）或直接重启（你自己）就生效，不用重新打包。

改装哪些插件：编辑 manifest.json。npm 里放包名和版本，local 里放 plugins/ 下的相对路径，shippedOptional 里放 Harness 自带的可选包名。

改我的设置模板：settings/preferences.patch.yml。现在里面是中文界面、详细对话视图、默认 grok-4.7 + xhigh 推理、加了一个插件市场索引。只在你的 cordis.patch.yml 还是空模板时才写入，你已经配置过就不动。

发布前跑一下公开检查，它会把本机路径、账号令牌这类不该进仓库的东西拦下来：

powershell -NoProfile -ExecutionPolicy Bypass -File scripts/check-public.ps1
git add -A
git commit -m "更新插件清单"
git push

需要注意的

• cordis.patch.yml 不在这里。那是你自己的运行时配置，需要的话单独拷
• WorkBuddy 要自己登录。形状看 settings/workbuddy.example.yml，填好的别提交
• 版本是照我这台机器锁的。装到别人机器上，npm 那些是同样的版本，我改过的和自建的（dsh-connect-workbuddy、dsh-image-viewer、harness-eval 等）是同一个仓库里的同一份源码，装出来跟我这边一致。升级 WorkBuddy 上游时按 plugins/dsh-connect-workbuddy/LOCAL-CHANGES.md 的流程走，别直接 dsh plugin add 覆盖
• 版本是按我这台机器锁的。你那边 Harness 如果缺某个实验包，会跳过；版本不兼容时 dsh 会拒绝安装，安装器不会自动做版本豁免——真要装得自己处理
• link: 插件的路径必须前后一致。profile 的 package.json 写绝对 link: 时，pnpm-lock.yaml 里那条 version 也必须是同一个绝对路径。它一旦变成 link:../../..，pnpm 按相对层级重建成指向别处的悬空软链接，DSH 启动就报 cannot resolve profile bundle——此时按提示重跑 dsh plugin install 没用，会把同一条坏记录再建一遍。要改锁文件里那行 version，再重建链接
• DSH home 是 junction 时，相对软链接只能活一半。这是同一个坑更难看见的形态：~/.dsh 指向别处（比如 D:/DSH-Home）时，profile 有两条路能到——应用按 ~/.dsh 启动，pnpm 在真实的盘上装。同盘的 link: 目标被 pnpm 写成相对路径（..\..\..\..\deepseek-harness\plugins\harness-eval），而相对路径是按「用哪条路走到它」解析的：从真实盘走能解开，从 ~/.dsh 走就悬空。表现是插件列表显示包不可用 / 包元信息错误，插件静悄悄地不再加载，但一切看起来都装好了。修法是把该链接换成绝对 junction：cmd /c rmdir "" 再 cmd /c mklink /J "" "<绝对目标>"
• 装完会自动查这件事。安装器最后跑 scripts/check-plugin-links.mjs：只要某条链接只在一条路上活着，就中止安装并给出修复命令。平时也可以直接跑它自查，一条命令看清每个 profile 的每条链接在两条路上是否都通
• Desktop 和官方包 appId 一样。已经在用自建包的机器，别再装官方安装包，会盖掉自建那份

不会放进来的

整个 profile、node_modules（唯一的例外是 plugins/dsh-connect-workbuddy/node_modules/@deepseek-ai/schemastery——这个包不在 profile 根上，不带就得自己装）、锁文件、WorkBuddy 账号、本机绝对路径、Harness 源码，都不在这个库。

我 fork 的 Harness 是 Aceared0829/deepseek-harness，引擎相关的改动在那里；这个库只管插件。

English

This is my DeepSeek Harness plugin set — the one I actually use every day — packaged so you can put it on your own Harness.

I keep it as a repo you can install from with one command. Take the whole set, take a few of the plugins, or fork it and maintain your own list.

> Looking for more Harness plugins? Search the dsh-plugin topic on GitHub.

What is in here

Plugins I wrote (sources live in this repo):

Plugins I modified (upstream is on npm; my changed sources are here too, and my copy is what gets installed):

Plugins by other people, installed from npm at the versions I pinned — I do not re-host their sources:

dsh-context, @modusensus/dsh-mneme (long-term memory), dsh-better-sidebar, @changfenhuang/dsh-genui (UI components), two from @goodandready/* (dsh-context-lens, dsh-time-machine), three from @linxin666/* (session-archive, usage, client-ui-model-capabilities), plus billion-context, dsh-claude-style, dsh-super-code, ds-bot, dsh-github-connect, @tt-a1i/archify-dsh, @deepseek-ai/dsh-subagent-claude-code, and @michengai/dsh-skills-manager.

The full list and versions are in manifest.json.

Two that run on my machine but are not this kit's business: kaoyan-workbench (its own repo, Aceared0829/kaoyan-workbench, linked into the profile) and @local/dsh-turn-autocontinue (a local bundle under default-workspace/bundles/ with no repo of its own). Neither is in the manifest, so the installer leaves both alone.

Experimental bundles that Harness ships disabled are switched on in my set: agent team, voice input, auto-review, inspector, the worktree tool, CoT translation, terminal, session search, session titles, the badge skill, ralph, the plugin market, and personalized recommendations. The installer checks whether your installation actually has each one and skips what is missing — it will not modify your Harness to force them in.

Installing it

You need DeepSeek Harness already installed and dsh available in your terminal. This repo does not install Harness itself.

Desktop users: register the dsh command in the app first, then quit completely from the tray. Closing the window is not enough — the Host keeps running in the background and the desktop profile cannot be written while it does.

git clone https://github.com/Aceared0829/dsh-kit.git
cd dsh-kit
.\install.ps1

macOS / Linux:

git clone https://github.com/Aceared0829/dsh-kit.git
cd dsh-kit
chmod +x install.sh
./install.sh --profile web

Reopen Harness when it finishes.

Common flags:

• -Profile desktop / --profile desktop — install into the Desktop profile. It refuses when the Desktop-bundled dsh cannot be found, so an ordinary CLI cannot corrupt that profile by accident
• -Profile web — install into the Web / terminal profile
• -DryRun — print the commands without touching the profile. Use this first if you want to see what will change
• -SkipPreferences — do not apply my settings template
• -Home — target a specific Harness home. Defaults to DSH_HOME, then ~/.dsh

The installer adds a few pnpm settings to your profile

On first install it writes a few keys into the profile's pnpm-workspace.yaml, because otherwise the install cannot complete:

• allowBuilds — permits the Harness runtime's native packages (node-pty, koffi, protobufjs, @deepseek-ai/dsh-subprocess-local, @google/genai), plus ssh2 and cpu-features, which are only needed once you add a plugin like dsh-ssh — approved up front so a later addition does not get blocked. pnpm 11 aborts the whole install when it finds an unapproved build script
• nodeLinker: hoisted and autoInstallPeers: false — matches the layout Harness itself uses for a profile

It only adds what you are missing. An existing profile is never rewritten, and the previous file is kept as pnpm-workspace.yaml.bak-dsh-kit.

Maintaining your own copy

Fork the repo, or just edit the clone you already have.

Change a plugin: the sources are under plugins/. They are installed as link: into your clone, so edits take effect on restart — no rebuild needed.

Change which plugins are installed: edit manifest.json. Put package names and versions under npm, repo-relative paths under local, and the names of Harness-bundled optional bundles under shippedOptional.

Change my settings template: settings/preferences.patch.yml. Right now it sets a Chinese UI, the verbose transcript view, grok-4.7 at xhigh reasoning effort, and one plugin-market index. It is only applied while your cordis.patch.yml is still the empty template; anything you have configured is left alone.

Before publishing, run the public check — it rejects machine paths, accounts, and tokens that should not reach a public repo:

powershell -NoProfile -ExecutionPolicy Bypass -File scripts/check-public.ps1
git add -A
git commit -m "Update the plugin list"
git push

Things worth knowing

• cordis.patch.yml is not included. That is your own runtime configuration; copy it separately if you want it
• WorkBuddy needs its own login. The shape is in settings/workbuddy.example.yml; do not commit a filled-in copy
• Versions are pinned against my machine. On someone else's box the npm entries resolve to the same versions, and the ones I modified or wrote myself (dsh-connect-workbuddy, dsh-image-viewer, harness-eval, …) come from the same sources in this repo, so an install lands on what I run. When upgrading WorkBuddy's upstream, follow plugins/dsh-connect-workbuddy/LOCAL-CHANGES.md — do not overwrite it with dsh plugin add
• A link: plugin needs the same path everywhere. When the profile's package.json declares an absolute link:, the matching version in pnpm-lock.yaml must be that same absolute path. If it turns into link:../../.., pnpm rebuilds it by relative depth into a dangling symlink somewhere else, and DSH refuses to boot with cannot resolve profile bundle; re-running dsh plugin install as the message suggests only recreates the same bad record. Fix that version line and rebuild the link
• Desktop and the official package share an appId. If you already run a self-built package, do not install the official build over it

What is deliberately not here

The whole profile, node_modules (one exception: plugins/dsh-connect-workbuddy/node_modules/@deepseek-ai/schemastery, which is not present at the profile root and would otherwise have to be installed separately), lockfiles, WorkBuddy accounts, absolute machine paths, and Harness sources stay out of this repo.

The Harness I run is my fork, Aceared0829/deepseek-harness. Engine changes go there; this repo is only about plugins.