Skip to main content

How to use dsh-web-plugin-manager

Web-based plugin manager for DeepSeek Harness: visually manage plugin start/stop, installation, updates, and uninstallation. Includes quality gates, health checks, and a third-party plugin marketplace.

This article is auto-derived from indexed fields (wiki / faq / compatibility_json), not freshly AI-generated.

This article is derived from the plugin's already-indexed fields (wiki / faq / compatibility_json / readme), not freshly generated by AI. Source field is noted at the end of each section.

Quick start

dsh-web-plugin-manager

— source: plugin_wiki.wiki_content

Install & verify

dsh plugin --profile web add dsh-web-plugin-manager

Run the command above in your DSH Web Profile. Then enable the plugin in the plugin list.

— source: plugins.install

Key points

  • add 不带版本号不会升级:profile 里已声明旧版本(如 ^0.1.2)时,dsh plugin add(即 pnpm add)保留原 specifier 不升;dsh plugin update(即 pnpm update)也只在已声明的范围内重解析。跨版本升级必须用 add ...@latest 或 dshpm update。
  • 分析引擎:src/analyze.ts —— 离线依赖图/冲突/兼容性分析(与质量门共享扫描器);运行时诊断读取 ctx.reflect 活跃服务表
  • Patch 编辑:src/patch.ts —— managed 标记块追加/移除(insert/disable 双类型识别)、行级操作、原子写入(tmp + rename);处理 YAML 陷阱(@ 包名引号、空数组文档、纯注释文件恢复模板)
  • 环境变量扫描:src/scan.ts —— git 源安装期 env 需求扫描(2 层/40 文件/8 变量上限)+ 子进程 env 敏感键剔除;src/installSession.ts 会话状态机(15 分钟 TTL、answers 白名单校验)
  • Agent 工具:src/tools.ts —— 依赖注入避免循环依赖;安装守卫 src/guard.ts 拒绝裸 dsh plugin/npm/yarn/bun/pnpm 变更命令(只读 verb 放行),拒绝原因直接指路 plugin_* 工具与 dshpm;systemPrompt.section 常驻提示同一条规则

— source: plugin_wiki.readme_en (fallback readme_raw)

FAQ

What is the relationship between this plugin and the official built-in plugin list?

It will explicitly disable the official read-only plugin manifest ui-settings-plugin-inventory via cordis.patch.yml (only effective during this plugin's installation, automatically restored after uninstallation), and registers its own 'catalog' and 'manager' Tabs instead.

Do I need to install this first before installing other plugins?

The official README strongly recommends installing it first: the manager's quality gate and health checks will perform dependency graph, conflict, and peer compatibility checks during each subsequent installation/runtime; installation failures will automatically roll back, significantly reducing the risk of 'installing and breaking'.

Should I use manual dsh plugin add or go through this plugin for installation?

Should install through the 'Plugin Management' Tab in Web UI or dshpm CLI, with all changes following the same protected path (pnpm + quality gate + automatic rollback); bare dsh plugin add will pass the quality gate but lose protection.

Can it update itself?

Yes. In 'Settings → Plugin Management', clicking 'Check for Updates' will list all installed plugins including the manager itself; click update on the corresponding card, failures will automatically reinstall the previous version, and a profile restart is required for updates to take effect.

Which DSH versions are supported?

peerDependencies require @deepseek-ai/cordis ^4.0.1, @deepseek-ai/dsh-tools ^0.1.0-rc.6, @deepseek-ai/schemastery ^3.18.1, js-yaml ^4.3.1.

Can it work across macOS/Windows/Linux?

The server side is pure Node, running cross-platform; the browser side is injected into the Web profile via dsh.client.platform=web.

What if the AI Agent is blocked from installing plugins?

This is expected behavior: guard.ts will reject bare dsh plugin/pnpm/npm/yarn/bun write commands and prompt to use plugin_install / plugin_uninstall / plugin_toggle tools or dshpm CLI, so changes go through the quality gate and rollback.

Where does the plugin marketplace data come from?

registry.ts prioritizes reading the community DSH-Plugins-Marketplace static index (~3100 entries), overlaying awesome-dsh-plugins curated metadata and dsh.so L1-L5 verification badges; the server side determines if installed by two-way comparison of package name/repository.

— source: plugin_wiki.faq_json

Compatibility

  • DSH: 0.1.0-rc.6+(peerDependencies: @deepseek-ai/dsh-tools ^0.1.0-rc.6、@deepseek-ai/cordis ^4.0.1)
  • Node: 未声明(devDependencies 使用 @types/node ^22.0.0)

— source: plugin_wiki.compatibility_json

Pitfalls

Review the upstream repo before installing. This guide is auto-derived from indexed fields and may lag the latest release. If anything contradicts the official docs, treat the upstream source as authoritative.

— source: general rule