Skip to main content

How to use plugin-registry

The Thin Console adds a Plugin Management panel to the DSH Web settings page with 4 agent tools, enabling unified management of profile plugin installation states—bundle layer stack and insert rows—without modifying any official source code.

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

plugin-registry

— source: plugin_wiki.wiki_content

Install & verify

dsh plugin --profile web add @vlln/plugin-console

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

— source: plugins.install

Key points

— source: plugin_wiki.readme_en (fallback readme_raw)

FAQ

Where can I see the management panel in DSH Web after installation?

After installation, refresh the Web page. In the settings page, there will be a new tab called "Plugin Management" (separate from and parallel to the official "Plugins" tab). Clicking it loads the panel (packages/plugin/console/src/client/index.ts:45-57 / Panel.tsx:300).

Why don't non-bundle plugins require restarting DSH after installation?

The panel writes to the insert lines of profile cordis.patch.yml; starting from DSH 0811, profile-boot mounts a watch-only HMR instance, so line additions/deletions take effect in real-time without restarting the web (packages/plugin/console/src/index.ts:94-145 / README.zh.md:74-78).

Why do bundle plugins require restarting the web after installation?

Bundle plugins are installed in the profile package.json dependencies + dsh.profile.bundles layer stack. The layer stack is synthesized at startup and cannot be hot-swapped at runtime; the web must be restarted for changes to take effect (packages/plugin/console/src/index.ts:340-380 / README.zh.md:74-78).

How does agent use this installation mechanism? Do I need to switch to the panel?

No need. Node half registers 4 defineTool tools simultaneously (plugin_search / plugin_install / plugin_uninstall / plugin_status), sharing the same installation state with the panel, so agents can call them directly (packages/plugin/console/src/discovery/tools.ts:98-335).

How to distinguish the three states of the panel: Running/Preset Mount/Disabled?

Running = host enabled; Preset Mount = host disabled but agent preset still mounted (starting from 0811, model-side tools go through the preset channel, disabling host doesn't mean tools disappear); Disabled = neither host nor preset is mounted (packages/plugin/console/src/client/Panel.tsx:98-102).

Can I disable or uninstall this management tool in the panel?

No. Node half hard-bans operations on @vlln/plugin-console in toggle/remove routes, returning 409 — to prevent the management入口 self-destruction (packages/plugin/console/src/index.ts:752-754 / 826-829).

What does the error message 'pnpm add succeeded but X is not in the profile dependencies' mean when installation fails?

Usually the git source or path source didn't actually land on disk (pnpm exited 0 but dependencies weren't written to package.json). It won't continue writing the installation state to avoid false success; use an explicit npm package name or confirm git/path is reachable before retrying (packages/plugin/console/src/index.ts:720-724 / discovery/tools.ts:196-199).

How to update when there's a new version of the plugin?

Clicking the "Check for Updates" button in the panel triggers the Node half to check the npm registry using native fetch (30-second minimum debounce). For bundles, an "Update" button appears, which runs pnpm update; git/link sources are marked as "local" with no latest version (packages/plugin/console/src/versions.ts:36-47 / Panel.tsx:208-226).

— source: plugin_wiki.faq_json

Compatibility

  • DSH: ^0.1.0-rc.5(peerDependencies 声明 @deepseek-ai/dsh-tools ^0.1.0-rc.5,依赖 web profile 的 webServer / loader / tools / agentPresets 四个 inject 服务,对应 0811 之后官方移除 repository-plugins 机制的版本)
  • Node: 未在 packages/plugin/console/package.json 声明 engines.node(devDependencies 中 @types/node ^22.0.0,建议 Node ≥ 22)

— 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