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 plugin is a sub-package of the vlln/plugin-registry monorepo — stars and activity count the whole repository.
- Language
- TypeScript
- License
- MIT
- Branch
- main
Install
$ dsh plugin --profile web add @vlln/plugin-consoleRun 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/rthree formats auto-normalized), automatically route based on whether the package declaresdsh.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 viadefineTool, 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.ymlinsert rows; bundle plugins write to profilepackage.jsondependencies anddsh.profile.bundleslayer 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 registrationdefineTool) /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-consolecordis plugin viadsh.bundle.patch, mounted to web profile'swebServer(/api/plugin-consoleroute) +loader(reads loader tree entries) +tools(registers 4 agent tools) +agentPresets(preset mount tagging) four inject services; Browser half mounts React panel tosettings.sectionslot viadsh.client.inject - Entry Files:
packages/plugin/console/src/index.ts(Node half, exportsname = 'plugin-console'andinject = ['webServer', 'loader', 'tools', 'agentPresets']) /packages/plugin/console/src/client/index.ts(Browser half, exportsname = 'plugin-console-client'andinject = ['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
| Dependency | Minimum Version | Description |
|---|---|---|
| DSH | ^0.1.0-rc.5 | peerDependencies 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 |
| Node | Not declared | package.json does not declare engines.node; devDependencies @types/node ^22.0.0, recommends Node ≥ 22 (aligns with DSH 0811 host baseline) |
| Platform | Web | dsh.client.platform: "web"; Node half is cross-platform but only registers routes under web profile combination |
| Native Modules | None | Only 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
| Config | Type | Description | Default |
|---|---|---|---|
| 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.ymlis deleted to empty, HMR fails to reload because YAML parses tonull— 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 patchnamefield 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/npmcommands called via.cmdbatch wrapper trigger libuv EINVAL; Node half changed to directly spawn<node>\node_modules\npm\bin\npm-cli.jsor%APPDATA%\npm\node_modules\pnpm\bin\pnpm.mjsJS entry, falling back to.cmdwhen entry not found (packages/plugin/console/src/index.ts:382-403). - Browser panel custom tab icon uses
MutationObserverto 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
agentPresetsservice 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/refreshwon'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).
plugin-registry
中文 | English
DSH plugin ecosystem infrastructure: thin console + official plugin development guide
Browser panel managing a profile's plugin install state (bundle layer stack + insert rows + enable/disable), zero patches;
the `make-dsh-plugin` skill guides developers in writing official-format plugins.
Pivot (2026-08): Official 0809 added a repository plugin mechanism (
.dsh-plugin) covering ~95% of the old mechanism; this repo is now a thin console + plugin development spec and guidance (old patches/CLI/panel removed). Since 0811 the repository-plugins mechanism is gone (vendor/loader/src/repository.ts); external plugins install via the web profile only: bundles (dsh.bundle) joindsh.profile.bundles; non-bundles (plain cordis packages) mount via insert rows incordis.patch.yml(live via HMR). Full assessment: official 0809 coverage.
Positioning
DeepSeek Harness's official mechanisms define "what a plugin is and how it runs"; this repository adds two things (panel structure: console README; guidance: below):
- Thin console (
packages/plugin/console) — browser panel managing a profile's plugin install state + 4 agent tools - Development spec and guidance —
make-dsh-pluginskill + cookbook for creating official bundle/cordis plugins
Ecosystem relationships (who can do what)
Official DSH (DeepSeek Harness) plugin runtime + profile bundle mechanism (no repo mechanism since 0811)
│
├── Official plugins (bundle) loop / task-status / navbar etc. — `dsh plugin --profile web add` install into profile layer stack
├── Third-party plugins (bundle/plain) standalone GitHub repos or npm packages — bundles enter the layer stack; plain plugins use insert rows (live)
│
└── This repository (plugin-registry) ① thin console: browser panel + agent tools for install-state management
② make-dsh-plugin skill + cookbook: guides third-party plugin development
Plugin forms and install paths: plugin type comparison; install examples: examples.
Thin console

The settings page's "Plugin Management" panel manages a profile's plugin install state: install area (single entry — npm package name or GitHub project (https://github.com/o/r / github.com/o/r / github:o/r, URL auto-normalized) — automatic pnpm add; bundles enter the layer stack, non-bundles get insert rows) + loaded area (version check/update, disabled toggle, bundle uninstall).
Installation
Option 1: git source, direct install (recommended, one line)
dsh plugin --profile web add "github:vlln/plugin-registry#main&path:/packages/plugin/console"
Build artifacts are committed (git source skips the build); one command installs directly (~15 s).
Option 2: npm source
dsh plugin --profile web add @vlln/[email protected]
Option 3: local directory (source available)
git clone https://github.com/vlln/plugin-registry
cd plugin-registry/packages/plugin/console
dsh plugin --profile web add . # artifacts are committed, no build needed; the current dir is the bundle package dir (dsh anchors . to an absolute path)
Refresh the web page after mounting — the "Plugin Management" panel appears on the settings page.
Agent Skills
| Skill | Purpose |
|---|---|
| make-dsh-plugin | Create official bundle / cordis plugins: pick a form (skill package / MCP / Node tool / with UI) → declare dsh.bundle or plain apply → install-and-verify discipline. Details in references/; reference implementation: packages/plugin/console |
Before you start developing (pitfalls we've hit)
Key pitfalls (official packages not yet published, Node-half changes need a restart, host CSS overrides, etc.) and the full list: skill references/gotchas — read before developing.
Documentation
- Plugin type comparison — bundle vs plain cordis plugins: development/distribution/installation/management dimensions + how to choose
- Official 0809 coverage assessment — official mechanism coverage, pivot decision (0811 repository removal: CHANGELOG)
- Thin console design — design of unified installation-state management
- Historical mechanism docs (archived after the pivot): architecture (old), creating a plugin (old), manifest format (old), creating a repository-plugin (old), etc.
- Changelog / Roadmap
License
MIT License. See LICENSE.
Read the usage guide →
Install steps, key points, FAQ and compatibility for this plugin — auto-derived from indexed fields.
Listing badge
[](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.