plugin-registry

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) join dsh.profile.bundles; non-bundles (plain cordis packages) mount via insert rows in cordis.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):

1. Thin console (packages/plugin/console) — browser panel managing a profile's plugin install state + 4 agent tools
2. Development spec and guidance — make-dsh-plugin skill + 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/plugin-console@0.1.0

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

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.