DeepSeek Harness 插件

dsh-plugin-manager-osskn4w7

Manage DeepSeek Harness plugins from the web GUI and CLI: install, enable/disable, uninstall — no manual config-file editing. Writes your profile's cordis.patch.yml for you and applies changes live(英文原文)

跳到安装方式

来源信息

GitHub 仓库
OSSKn4w7/dsh-plugin-manager
最近更新
2026年8月15日
分类
插件市场与管理
GitHub stars
1
载体类型
plugin
目录证据
上游声明已找到 dsh.bundle
证据路径
package.json#dsh.bundle
核对版本
0.1.0-rc.8
上游核对日期
2026-08-20

该证据由上游目录提供。本站没有安装、运行或安全审核这个插件。

安装

默认先复制一段 Prompt,让 Agent 读 GitHub 仓库和源码;需要自己装时再切到命令。

复制这段 Prompt,发给 DSH、Codex 或其他 Agent,让它先读 GitHub 仓库和源码。

请先不要安装或执行任何命令。阅读这个插件的 GitHub 仓库、README 和关键源码,然后用清楚、直接的方式回答以下问题,帮助我判断它是否适合我的需求:

1. 这个插件是什么,解决什么问题;
2. 适合哪些用户和典型使用场景;
3. 安装后如何使用,并给出一个最小使用示例;
4. 有哪些已知限制,以及隐私、安全、兼容性或维护风险;
5. 给出“推荐 / 有条件推荐 / 不推荐”的明确建议和理由。

请区分仓库明确说明、根据源码推断和未知信息。证据不足时请明确说明,不要猜测或照抄 README。

GitHub:https://github.com/OSSKn4w7/dsh-plugin-manager
插件名:dsh-plugin-manager-osskn4w7
作者:OSSKn4w7

检查来源文件

安装前先看这个插件目录里的 README 和其他文件。

文件资源管理器3 个文件
README.md来源说明 · 只读预览

dsh-plugin-manager

Manage DeepSeek Harness plugins without editing config files.

The shipped workflow is: drop a package into the profile, hand-edit cordis.patch.yml, restart, repeat. This plugin gives the web GUI a 插件管理 (Manage) tab — right inside Settings → Plugins — where you can:

  • install a plugin by npm package name (with optional JSON config),
  • enable / disable any loader entry with one click (applied live, no restart),
  • uninstall plugins again,
  • see the whole composed Loader tree, the profile's dependencies and bundles,

and which rows the manager itself installed.

It writes your profile's cordis.patch.yml for you (a delimited auto-managed block; your hand-written patches are preserved byte-for-byte) and the running server's user-patch watcher (HMR) applies the change immediately.

It also ships a CLI (dsh-plugin-manager) and a chat command (/plugin).

Components

PieceRole
lib/index.jsHost half: JSON API under /plugin-manager/api + the /plugin chat command
lib/client.jsBrowser half: the 插件管理 tab in Settings → Plugins
lib/core.mjsShared logic: managed-block editing of cordis.patch.yml, pnpm runner, bundle reconcile
bin/dsh-plugin-manager.mjsStandalone CLI (works even while the server is stopped)

Install

npm: @osskn4w7/dsh-plugin-manager

# Option A — standard dsh bundle install:
dsh plugin --profile web add @osskn4w7/dsh-plugin-manager
# then restart dsh web (bundle patch layers load at boot)

# Option B — live install without a restart (from this checkout):
dsh-plugin-manager bootstrap --profile web
# or by hand: pnpm add file:… in the profile dir, then enable the entry,
# then refresh the browser (Settings → Plugins → 插件管理)

Use one option, not both (the row would be inserted twice). bootstrap installs this package into $DSH_HOME/profiles/web via pnpm and wires its Loader entry into cordis.patch.yml. Because the profile patch file is watched live, the host half activates immediately; refresh the browser once so the client bundle is picked up.

To use the CLI standalone (outside a profile checkout):

npm i -g @osskn4w7/dsh-plugin-manager
dsh-plugin-manager list --profile web

Requirements: pnpm on PATH, the web profile (or any profile with the web bundle), and a loopback-bound server (the default).

Publishing (maintainers)

The package lives on npm as @osskn4w7/dsh-plugin-manager and on GitHub as OSSKn4w7/dsh-plugin-manager.

npm version patch          # or minor / major — bumps version + git tag
npm publish --registry=https://registry.npmjs.org/ --access public
git push && git push --tags

Notes:

  • The default npm registry on this machine is an npmmirror mirror — always

pass --registry=https://registry.npmjs.org/ (mirrors are read-only).

  • The account has 2FA enabled (auth-and-writes): publish either with

--otp <code> or with a granular access token that has bypass 2FA enabled (create it at npmjs.com settings; its direct-publish ability is scheduled to end January 2027 in favor of a 2FA-approval flow).

  • The bin entry (dsh-plugin-manager) is included in the published tarball

via the package's files whitelist.

How enabling/disabling works

  • Plain plugin (no dsh.bundle in its manifest): install runs

pnpm add and inserts a live Loader entry into the managed block — enabled immediately.

  • Bundle plugin (declares dsh.bundle): install runs pnpm add and

reconciles the name into dsh.profile.bundles in package.json (same rule as dsh plugin --profile … add). Bundle patch layers are read at boot, so it reports needsRestart; after restart its entries appear and can be toggled.

  • Enable/disable: adds/removes an id-targeted disabled patch in the

managed block. The watcher recomposes the tree live.

CLI

dsh-plugin-manager list [--json] [--profile web]
dsh-plugin-manager enable <entry-id>   # or: disable
dsh-plugin-manager install <pkg> [--config '{"a":1}']
dsh-plugin-manager remove <pkg>
dsh-plugin-manager bootstrap

Chat command

In the web chat, /plugin list, /plugin enable <id>, /plugin disable <id>, /plugin install <pkg>, /plugin remove <pkg>.

Notes

  • The managed block in cordis.patch.yml is delimited by

# >>> dsh-plugin-manager … >>> / # <<< dsh-plugin-manager <<<; edits inside it are overwritten. Everything outside is yours.

  • The HTTP API is loopback-only (matching the server's default bind) and

carries no auth — do not expose the web server to a network you do not trust.

  • A disabled row whose id no longer exists in the composed tree logs a benign

loader warning; the manager drops such patches for packages it uninstalls.

License

MIT