Back to directory

plugin-registry

Curated pickMaintenance: Active

vlln/plugin-registry

DSH 插件生态基建:薄控制台(浏览器面板管理 profile 插件安装态/bundle 层栈/启停)+ make-dsh-plugin skill 官方插件开发引导。

View on GitHub
$ dsh plugin --profile web add "github:vlln/plugin-registry#path:/packages/plugin/console"

58

stars

6

forks

TypeScript

Language

MIT

License

2026-08-04

Created

2026-09-21

Last push

MIT-licensed DeepSeek Harness infrastructure: a thin browser console for managing a profile's plugin install state plus the `make-dsh-plugin` skill for authoring official bundle / cordis plugins.

DSH integration

Native runtime

Author-claimed

Safety audit

Unaudited

Last verified

2026-09-02

License

MIT

01What can it help you accomplish?

  • Manage a DeepSeek Harness profile's plugin install state from a browser panel

    A settings-page "Plugin Management" panel: an install area (npm name / GitHub project) and a loaded area (version check/update, disable toggle, bundle uninstall); bundles enter the layer stack, non-bundles get insert rows

    DSH profile operators and power users who install third-party plugins through the web profile

  • Develop official-format DeepSeek Harness plugins

    The `make-dsh-plugin` skill + cookbook that guides creating official bundle / cordis plugins (skill package / MCP / Node tool / with UI)

    Plugin authors who want to publish bundle or cordis plugins for DeepSeek Harness

02How to install into DeepSeek Harness

Prerequisites

  • DeepSeek Harness (`dsh`) CLI available on your PATH — every install command in the README calls `dsh plugin --profile web add`
  • A web profile to install into (the README uses `--profile web`)

Installation steps

  1. 01

    Recommended (git source, one line): `dsh plugin --profile web add "github:vlln/plugin-registry#path:/packages/plugin/console"`

    $ dsh plugin --profile web add "github:vlln/plugin-registry#path:/packages/plugin/console"

  2. 02

    $ npm source: `dsh plugin --profile web add @vlln/plugin-console@0.1.0`

  3. 03

    Local directory: `git clone https://github.com/vlln/plugin-registry`, `cd plugin-registry/packages/plugin/console`, then `dsh plugin --profile web add .`

    $ git clone https://github.com/vlln/plugin-registry

  4. 04

    Refresh the web page after mounting so the "Plugin Management" panel appears on the settings page

Verify the integration

  • After mounting, refresh the web page — the "Plugin Management" panel appears on the settings page

03DSH integration and capability boundaries

DSH integrationNative runtime

Thin console (cordis bundle) installed into a DeepSeek Harness web profile via `dsh plugin --profile web add`; adds a browser panel + 4 agent tools for install-state management and ships the `make-dsh-plugin` skill for building official plugins.

  • Thin console — Plugin Management panel

    npm package name or GitHub project URL (`https://github.com/o/r` / `github.com/o/r` / `github:o/r`, auto-normalized)→Profile install state: bundles enter the layer stack, non-bundles get insert rows; loaded area offers version check/update, disable toggle, uninstall

    Automatic `pnpm add` of the named package
  • make-dsh-plugin skill + cookbook

    A plugin idea and a chosen form (skill package / MCP / Node tool / with UI)→An official bundle / cordis plugin scaffold following the `dsh.bundle` or plain-apply spec, with install-and-verify discipline

  • 4 agent tools for install-state management

    Agent tool calls from a DeepSeek Harness session→Install-state management actions (install / enable / disable / update) surfaced through the same console

04Who is it for? When not to use it?

Good for

  • DSH profile operators and power users who install third-party plugins through the web profile
  • Plugin authors who want to publish bundle or cordis plugins for DeepSeek Harness

Not for

  • On Windows use the `#path:` install form, not `#main&path:...`: win32 `dsh plugin` forwards args through cmd.exe where `&` is a command separator, so `#main&path:...` gets split and fails with ERR_PNPM_INVALID_DEPENDENCY_NAME.

05Compatibility, maintenance and safety notes

  • On Windows use the `#path:` install form, not `#main&path:...`: win32 `dsh plugin` forwards args through cmd.exe where `&` is a command separator, so `#main&path:...` gets split and fails with ERR_PNPM_INVALID_DEPENDENCY_NAME.
  • Since 0811 the official repository-plugins mechanism is gone; external plugins (including this console) install via the web profile only — bundles join `dsh.profile.bundles`, non-bundles mount via insert rows in `cordis.patch.yml`.
  • Changes to the Node (runtime) half of a plugin require a restart to take effect — the README points to a gotchas doc to read before developing.
2026-08-042026-08-30Not specified by the author

MIT License; pivoted 2026-08 to a thin console + plugin development spec (repository-plugins mechanism removed since 0811)

06Frequently asked questions

How do I install the plugin-registry console into DeepSeek Harness?

Recommended git source, one line: `dsh plugin --profile web add "github:vlln/plugin-registry#path:/packages/plugin/console"`; or npm `dsh plugin --profile web add @vlln/plugin-console@0.1.0`; or clone then `dsh plugin --profile web add .` (local dir). Refresh the web page after mounting.

What does the thin console do in DeepSeek Harness?

It adds a "Plugin Management" panel to the settings page that manages a profile's plugin install state — an install area (npm name / GitHub project) and a loaded area (version check/update, disable toggle, bundle uninstall); bundles enter the layer stack, non-bundles get insert rows.

Does plugin-registry still install plugins as repository-plugins?

No — since 0811 the official repository-plugins mechanism is gone; external plugins (including this console) install via the web profile only. Bundles join `dsh.profile.bundles`, non-bundles mount via insert rows in `cordis.patch.yml`.

How do I build a DeepSeek Harness plugin with this repo?

Use the `make-dsh-plugin` skill + cookbook: pick a form (skill package / MCP / Node tool / with UI), declare `dsh.bundle` or plain apply, then follow the install-and-verify discipline.

On Windows, why does the `#main&path:...` install form fail?

On win32 `dsh plugin` forwards args through cmd.exe where `&` is a command separator, so `#main&path:...` gets split and fails with ERR_PNPM_INVALID_DEPENDENCY_NAME; use the `#path:` form instead.

08Data and sources

  • Author-claimedgithub.comd581b3df4054…

    DeepSeek Harness's official mechanisms define "what a plugin is and how it runs"; this repository adds two things

  • Author-claimedgithub.comd581b3df4054…

    1. **Thin console** (`packages/plugin/console`) — browser panel managing a profile's plugin install state + 4 agent tool…

This page is generated from the project’s public documentation, repository metadata and a structured parse of DSH Plugins; last verified on 2026-09-02. Found an error? Submit a correction.

🏆

Best DeepSeek Harness Plugins

Twelve plugins worth installing first — picked from the whole catalog, across every category.

DSH Plugins is an independent community directory of DeepSeek Harness plugins. Not affiliated with or endorsed by DeepSeek. Third-party plugins are not security-audited — review the source before installing.

New DeepSeek Harness plugins, weekly. No spam.