Skip to main content

plugin-registry/packages/plugin/console

57Stars6Forks1Issues0Watchers

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.

Evidence5/5methodologySourceInstallMaintenanceDSH versionSecurity scan
Machine-auditedInstall commandRepo verifieddsh-plugin topicLicenseREADMEAI wiki

ⓘ This plugin is a sub-package of the vlln/plugin-registry monorepo — stars and activity count the whole repository.

Language
TypeScript
License
MIT
Branch
main
consoledeepseek-harnessdshdsh-plugindsh-repository-pluginplugin-managementui

Install

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

Run the command above in your terminal to install this plugin via the dsh CLI. You can switch Profile in the top-right corner. New to dsh? Read the beginner tutorial

Install via your agent

Install the DeepSeek Harness plugin vlln/plugin-registry/packages/plugin/console for me: review the repository at https://github.com/vlln/plugin-registry first, then run the install command and verify the plugin loads successfully.

Paste this instruction to the DSH Web GUI assistant — it will install and verify for you.

One-line Positioning

The thin console moves plugin management into the DSH Web Settings page: the panel uniformly handles both bundle and non-bundle plugin installation states, plus 4 agent tools share the same storage, without modifying any official source code throughout.

Core Capabilities

  • Add a "Plugin Management" tab to the DSH Web Settings page, listing all loaded plugins grouped by user/official built-in, supporting runtime enable/disable, version checking, bundle updates and uninstallation
  • One-line installation entry: input npm package name or GitHub project (https://github.com/o/r / github.com/o/r / github:o/r three formats auto-normalized), automatically route based on whether the package declares dsh.bundle: bundle goes to layer stack (restart takes effect), non-bundle writes insert row (config HMR real-time mount)
  • 4 agent tools (plugin_search / plugin_install / plugin_uninstall / plugin_status) registered via defineTool, writing to the same installation state as the panel, supporting command-line batch operations
  • npm registry version check: native fetch to check latest version (no subprocess, usable in restricted hosts), 30-second minimum interval debounce, git/link sources automatically identified as "local" without latest
  • TOFU lock records installation source reference ($DSH_HOME/plugin-sources/lock.yml) + index source collection (sources.yml, supports hub catalog and local/URL custom source lazy loading)
  • Transparent write location: non-bundle plugins write to profile cordis.patch.yml insert rows; bundle plugins write to profile package.json dependencies and dsh.profile.bundles layer stack

Technical Implementation

  • Language: TypeScript (Node half) + TypeScript + React 18 (Browser half)
  • Key Dependencies: cordis ^4.0.0-rc.7 (host half plugin runtime) / @deepseek-ai/dsh-tools ^0.1.0-rc.5 (agent tool registration defineTool) / react ^18.2.0 (browser half panel UI) / yaml ^2.4.0 (profile patch and sources.yml parsing and writing)
  • Architecture Pattern: Official bundle dual-half plugin — Node half registers plugin-console cordis plugin via dsh.bundle.patch, mounted to web profile's webServer (/api/plugin-console route) + loader (reads loader tree entries) + tools (registers 4 agent tools) + agentPresets (preset mount tagging) four inject services; Browser half mounts React panel to settings.section slot via dsh.client.inject
  • Entry Files: packages/plugin/console/src/index.ts (Node half, exports name = 'plugin-console' and inject = ['webServer', 'loader', 'tools', 'agentPresets']) / packages/plugin/console/src/client/index.ts (Browser half, exports name = 'plugin-console-client' and inject = ['slots']) / packages/plugin/console/cordis.patch.yml (bundle injection declaration)

Applicable Scenarios

DSH users who have multiple third-party bundle or non-bundle plugins installed and need to centrally view, enable/disable, and update them in the Web UI, without manually modifying profile configurations or restarting services one by one. Agent developers who need to automatically install/uninstall plugins within controlled DSH processes (e.g., setup flow, CI plugin validation), preferring to use official mechanisms instead of bypassing pnpm. When trying different plugin combinations without manually writing YAML in cordis.patch.yml each time — the panel and tools directly take over installation state read/write.

Prerequisites & Compatibility

DependencyMinimum VersionDescription
DSH^0.1.0-rc.5peerDependencies declares @deepseek-ai/dsh-tools ^0.1.0-rc.5; depends on web profile's webServer / loader / tools / agentPresets four inject services, corresponding to versions after 0811 where official removed repository-plugins mechanism
NodeNot declaredpackage.json does not declare engines.node; devDependencies @types/node ^22.0.0, recommends Node ≥ 22 (aligns with DSH 0811 host baseline)
PlatformWebdsh.client.platform: "web"; Node half is cross-platform but only registers routes under web profile combination
Native ModulesNoneOnly uses node:fs / node:child_process / node:os / node:path built-in modules and browser fetch, no native bindings introduced

Installation

dsh plugin --profile web add github:vlln/plugin-registry/packages/plugin/console

Configuration Options

ConfigTypeDescriptionDefault
None-This plugin does not expose Cordis schema configuration items; behavioral parameters (DSH_HOME resolution, profile directory, registry timeout 15s, 30-second startup delay pre-scan, npm_config_registry mirror compatibility, etc.) are all source code constants-

FAQ

Q: Where can I find the management panel in DSH Web after installation?

A: After installation, refresh the Web page, and a "Plugin Management" tab will appear in the Settings page (next to the official "Plugins" tab). Click to load the panel.

Q: Why don't non-bundle plugins require DSH restart after installation?

A: The panel writes to profile cordis.patch.yml insert rows; starting from DSH 0811, profile-boot mounts a watch-only HMR instance, so write/delete rows take effect in real-time.

Q: Why do bundle plugins require web restart after installation?

A: Bundle plugins are installed in profile package.json dependencies + dsh.profile.bundles layer stack; the layer stack is assembled at startup and cannot be hot-swapped at runtime.

Q: How do agents use this installation mechanism? Do they need to switch to the panel?

A: No. The Node half simultaneously registers 4 defineTool tools (plugin_search / plugin_install / plugin_uninstall / plugin_status), writing to the same installation state as the panel.

Q: How to distinguish the three states "Running/Preset Mounted/Disabled" in the panel?

A: Running = host enabled; Preset Mounted = host disabled but agent preset still mounted (0811 model face tools go through preset channel, disabling host doesn't mean tools disappear); Disabled = completely disabled.

Q: Can I disable or uninstall this management tool itself from the panel?

A: No. The Node half hardcodes prohibition on @vlln/plugin-console operations in toggle/remove routes, returning 409 — to prevent the management entry from self-destructing.

Q: What does "pnpm add succeeded but X is not in the profile dependencies" mean when installation fails?

A: Usually the git source or path source didn't actually land on disk (pnpm exited 0 but dependency wasn't written to package.json), so the installation state won't be written to avoid false success; use an explicit package name or confirm git/path is reachable before retrying.

Q: How to update when a plugin has a new version?

A: Click the "Check Updates" button in the panel to trigger Node half to query npm registry via native fetch (30-second minimum interval debounce), bundle shows "Update" button, clicking it runs pnpm update; git/link packages marked as "local" without latest.

Difficulty Level

Beginner — works out of the box after installation, no configuration; advanced users automate via agent tools without reading source code.

Known Issues & Limitations

  • Bundle plugin install/update/uninstall requires web restart (layer stack assembled at startup), runtime only supports enable/disable; only non-bundle plugins (insert rows) support real-time mounting (packages/plugin/console/README.zh.md:74-78).
  • Node half changes require web restart (ESM cache), Browser half changes only need reinstall + page refresh (packages/plugin/console/README.zh.md:74-78).
  • When profile cordis.patch.yml is deleted to empty, HMR fails to reload because YAML parses to null — Node half write logic keeps comment + [] template as fallback (packages/plugin/console/src/index.ts:206-211).
  • If installation source string is npm scoped package (e.g., @scope/name), profile patch name field must be quoted — @ is a reserved indicator in YAML, unquoted causes HMR to not take effect (packages/plugin/console/src/index.ts:140-145).
  • On Windows, pnpm / npm commands called via .cmd batch wrapper trigger libuv EINVAL; Node half changed to directly spawn <node>\node_modules\npm\bin\npm-cli.js or %APPDATA%\npm\node_modules\pnpm\bin\pnpm.mjs JS entry, falling back to .cmd when entry not found (packages/plugin/console/src/index.ts:382-403).
  • Browser panel custom tab icon uses MutationObserver to listen for DOM replacement, only matching text "Plugin Management" (won't mistakenly change official "Plugins" tab gear icon), previously had icon mistakenly replaced due to name collision (packages/plugin/console/src/client/index.ts:18-42).
  • "Preset Mounted" tagging for loaded plugins depends on host agentPresets service being readable; when service unavailable, degrades to normal disabled state (packages/plugin/console/src/index.ts:484-498).
  • Version check has 30-second minimum interval debounce (/api/plugin-console/versions/refresh won't repeatedly hit registry in same process), first panel access uses delayed pre-scan 30 seconds after startup to populate cache (packages/plugin/console/src/index.ts:538-570).

Read the usage guide →

Install steps, key points, FAQ and compatibility for this plugin — auto-derived from indexed fields.

Listing badge

Listed on deepseek-plugin.org
[![Listed on deepseek-plugin.org](https://img.shields.io/badge/listed_on-deepseek--plugin.org-007EC6)](https://deepseek-plugin.org/plugins/vlln/plugin-registry/packages/plugin/console)

Paste this markdown into your GitHub README to link back to this listing. The badge only states the listing — not a security endorsement.

← Back to plugin directory