DSH Marketplace
中文

plugin-registry

vlln/plugin-registry

Ecosystem infrastructure: a thin browser console for managing official repository plugins (zero patches) plus a make-dsh-plugin skill for guided plugin development.

586TypeScriptMITSource

Install

Add plugin-registry to DeepSeek Harness

via GitHub · GitHub source

Installing from GitHub runs the project's build script, which pnpm blocks until you allowlist it — run the command once and pnpm prints the exact key to add under `allowBuilds` in ~/.dsh/profiles/web/pnpm-workspace.yaml.

What happened when we ran it

Installed cleanly when we ran it

Every command here is run in a throwaway container against a clean profile, and the result is whatever the harness recorded — not a guess from the source. Last run 14d ago.

Show it in your README

install verified — dshmarketplace

For maintainers: the badge serves this listing's latest sandbox verdict, so a re-run updates it on its own — and it links readers to the full result here.

Due diligence

Before you install plugin-registry

  • Source of record: vlln/plugin-registry — present in the community registry that DSH's own plugin market installs from.
  • Licensed under MIT.
  • A listing here is not a security review. Plugins run with your agent's permissions.

The AI take

What it is — It is infrastructure providing a thin browser console and make-dsh-plugin skill for the DeepSeek Harness plugin ecosystem.

Who it is for — If you need to manage plugin installation states in your DeepSeek Harness profile and want the make-dsh-plugin skill for developing official plugins, this fits.

If you only use existing plugins without needing management or development tools, you don't need this because it focuses on ecosystem infrastructure rather than direct runtime features.

Watch out — It was tested to install successfully in a fresh profile and register with harness.

Note the specific #path: format required for git source installation on Windows to prevent command splitting.

No other obvious issues found.

The verdict — I wouldn't install it because it serves as infrastructure rather than a functional plugin; if your use case doesn't involve plugin development or state management, it's not worth it.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.

What plugin-registry does

Abstract diagram of packages splitting into bundle and configuration paths before converging into one layered structure.

plugin-registry is a DeepSeek Harness plugin that adds a thin browser console for managing plugins in a profile and provides the make-dsh-plugin skill for plugin development.

The console works with the web profile’s existing installation mechanism rather than applying patches. Its install area accepts an npm package name or a GitHub repository reference, normalises the reference, and runs the profile installation flow. Bundle packages are added to the dsh.profile.bundles layer stack; non-bundle Cordis packages are mounted through an insert entry in cordis.patch.yml, where configuration hot reload applies changes. The loaded-plugin area supports version checks, updates, persistent disabled state, and bundle removal. The console also exposes four agent tools for managing this state.

DeepSeek Harness already supplies the plugin runtime and profile bundle mechanism, so plugin-registry is not a replacement runtime or a return of the removed repository-plugins mechanism. It is aimed at developers who want browser-based profile management or guided creation of official-format bundle and Cordis plugins. It is the wrong choice when the built-in profile installation flow is sufficient, or when a project needs the former repository-plugin system rather than the current web-profile path.

plugin-registry documentation

How plugin-registry behaves

DeepSeek Harness loads the console into the web profile. After the plugin is mounted and the Web page is refreshed, a 插件管理 panel appears in the settings page. The panel has two areas:

  • The install area accepts an npm package name or https://github.com/o/r, github.com/o/r, or github:o/r repository reference. GitHub references are normalised before the profile installation flow runs.
  • The loaded-plugin area checks versions, performs updates, persists disabled state, and uninstalls bundle plugins.

The console also provides four agent tools for managing the profile’s plugin installation state.

Configuring plugin-registry

The console writes to the profile structures used by DeepSeek Harness:

  • Bundle plugins enter the dsh.profile.bundles layer stack.
  • Non-bundle, pure Cordis plugins are mounted through an insert entry in cordis.patch.yml.

Changes to the insert configuration take effect through configuration HMR. The README does not specify additional configuration keys or defaults for plugin-registry.

Commands and development guidance

The profile-scoped add operation is the installation entry point used by DeepSeek Harness. The console accepts npm and GitHub sources through that flow; it does not describe a separate package registry or historical repository-plugin command.

The make-dsh-plugin skill documents how to create either an official bundle or a pure Cordis plugin. Its guidance covers choosing a plugin shape, declaring dsh.bundle or a pure apply, and verifying installation. Supporting detail is kept under skills/make-dsh-plugin/references/, including gotchas.md; the console itself is the repository’s reference implementation.

Known limits

The current design depends on DeepSeek Harness profile installation, specifically the web profile for the documented console setup. The former repository-plugins mechanism was removed upstream; plugin-registry does not restore it and instead uses bundle layers or cordis.patch.yml insert entries.

Written from the project's own documentation and kept in sync with it. Where the two disagree, the source is authoritative — read the README on GitHub

Same category

Alternatives to plugin-registry

dsh-routing-suite

yjh051108

7.0k

One repository, three parts: a runtime injector for DSH plugin packages (inject, hot-reload, unload, promote a dev staging tool to the front, route self-heal, plus a settings-page plugin manager that lists, unloads and drags folders in to internalize), a task-aware reasoning-mode router agent preset (router-standard / router-spec / router-react), and a graded two-level task protocol whose six tools (commit_star, lock_stage, revise_do, edit_plan, mark_task, redteam_verdict) pin task state to disk. The injector implementation ships in-tree, so the install carries its own behaviour rather than a dependency list.

Installs, but needs a build approved first

GitHub sourceJavaScript15d ago

AI review

dsh-routing-suite

What it is — dsh-routing-suite provides runtime injector and router-standard presets.

Who it is for — You can install this if you need to use router-standard task-aware reasoning-mode router presets in DeepSeek Harness. You can install this if you need to use router-spec presets in DeepSeek Harness.

Watch out — It requires source installation from GitHub. Sandbox testing passed when registered in a new profile. Static checks found no risks.

The verdict — I would install it because it provides the injector and router presets for DeepSeek Harness agent management.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
Source

mirage

strukto-ai

3.7k

Swaps the filesystem and bash providers for a mirage virtual workspace: file tools and shell commands run over mounted resources (RAM, S3, Redis, Slack, Gmail, Notion, Postgres) instead of the host disk, with per-mount read/write/exec modes, per-command sandbox routing (monty, pyodide, quickjs in process; docker, e2b, daytona remote), and installed CLIs (git, gh, slack, linear, ntn, gws, or one you register) as head words in the virtual terminal.

No one-line install — this plugin lives inside a larger repository and publishes no npm package.

GitHub sourceTypeScript4d ago

AI review

mirage

What it is — mirage provides a unified virtual filesystem for AI agents, allowing bash tools to operate across mounted resources.

Who it is for — It is suitable for AI agents that use bash tools and need to access multiple backends such as S3 and Slack at the same time. It is not suitable for agents that only run on local filesystems without remote mounted services.

Watch out — No obvious issues found. There is a static check prompt indicating it will execute shell commands. Sandbox testing was not performed.

The verdict — I would not install it because sandbox testing was not performed.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
1Details

oh-dsh

hust-open-atom-club

325

Community distribution: TUI, desktop, and Web UI as one bundle with layered installation.

Installed cleanly when we ran it

GitHub sourceTypeScript21d ago

AI review

oh-dsh

What it is — oh-dsh provides a DSH runtime bundle for Desktop, Web and TUI interfaces, including Workspace, PTY terminal, Git Review and plugin market.

Who it is for — If you use DeepSeek Harness for local development and need unified cross-end interfaces and shared plugin ecosystem, then oh-dsh is suitable. If you mainly work in a single interface environment without needing multi-end consistency, then you can install the TUI-only or Web-only distribution.

Watch out — Sandbox test passed after installation into a fresh profile and registration in harness. No obvious issues found. Source installation requires manual allowance of the build script.

The verdict — I would install it because it unifies the three interfaces and local tools integration; the premise is accepting source installation from GitHub.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
1Details

pi2dsh

weijiafu14

210

Pi Host ABI compatibility engine: after one install, unmodified Pi extensions from npm mount as native DSH plugins with `dsh plugin add <pi-package>`. Verified end to end on stock DSH with pi-mcp-adapter (full MCP manager: OAuth, resources, prompts, MCP Apps, elicitation, sampling), @tintinweb/pi-subagents, pi-code, pi-hermes-memory and pi-background-tasks; `pi2dsh inspect` reports a package's compatibility before installing.

Installed cleanly when we ran it

npm packageTypeScript11d ago

AI review

pi2dsh

What it is — pi2dsh is a Pi host ABI compatibility engine that mounts unmodified Pi npm packages as native DSH plugins on DeepSeek Harness.

Who it is for — Pi plugin developers who want to run their npm packages unmodified on DeepSeek Harness should install it. Developers who are not involved in Pi plugin development do not need to install it.

Watch out — It was tested successfully in a new profile and registered into the profile. A restart of DeepSeek Harness is required. Installation may require manually approving build scripts if pnpm blocks them.

The verdict — I would install it if I need Pi ecosystem plugins on DeepSeek Harness because it provides unmodified compatibility.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
1Source

dsh-undo-savepoint

lire1131

153

Undo/redo & rollback system for DSH: every config change is auto-snapshotted; undo/redo/restore to any version from the WebUI or the offline CLI/GUI tools (works even when DSH fails to boot).

Installed cleanly when we ran it

npm packageJavaScript23d ago

AI review

dsh-undo-savepoint

What it is — DSH plugin providing undo/redo/rollback for config changes and plugin code, with WebUI and offline CLI/GUI support.

Who it is for — If you frequently modify config and plugin code in DeepSeek Harness and want to undo those changes via WebUI or offline tools, consider this plugin. If your DeepSeek Harness usage does not involve such modifications, you may not need this plugin.

Watch out — Sandbox test passed: installed in a fresh profile and registered by harness. No obvious pitfalls found.

The verdict — I would install it because it provides offline tools as a fallback when DSH fails to boot.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
1Source

dsh-skill-mcp-panel

Fishquito7

146

Manages DSH skills and MCP servers from the web settings: skill cards with hot enable/disable, workspace scopes, groups, batch migration and drag-and-drop import, plus stdio/HTTP MCP CRUD with connection tests, secret redaction and the unified dsh-panel CLI.

Installed cleanly when we ran it

npm packageJavaScript13d ago

AI review

dsh-skill-mcp-panel

What it is — DSH plugin that adds skill and MCP management panels to Web settings and provides unified dsh-panel CLI. Supports hot enable/disable, batch migration, drag-and-drop add, scoped operations, and CRUD for stdio/HTTP MCP servers.

Who it is for — If you are developing skills or configuring custom MCP servers in a DeepSeek Harness profile, this lets you handle everything directly in the settings page; if you only use built-in tools without needing extra panels or CLI subcommands, you do not need to install it.

Watch out — Installation from source requires manually enabling the build script. Sandbox testing passed with no other obvious issues found.

The verdict — Install if you need skill and MCP management integration; otherwise it is not worth it. The premise is that your profile involves more than just built-in tools.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
1Source