DeepSeek Harness Plugin Hub

Publish and manage complete Harness Profiles. Discover Plugins for your next setup.

Explore

PluginsPresetsDocsNews

Community

Publish a pluginContactReport an issue

Resources

Plugin Hub on GitHubDeepSeek HarnessSystem statusPrivacy notice
© 2026 DeepSeek Harness Plugin HubPowered byPaxTech

Independent and unofficial. Not affiliated with, authorized by, or endorsed by DeepSeek.

DeepSeek Harness Plugin Hub
ProfilesPluginsCategoriesNewsDocsSign inManage Profiles
ProfilesPluginsCategoriesNewsDocsSign in
All documentation

Get started

Distribute a Carefully Tuned Agent Harness with PresetsWrite Your First DSH Plugin

Architecture

The Cordis Plugin Model Behind DSHFrom a Service to a Complete Agent CapabilityHow Bundles, Profiles, and Patches Compose DSHWhy DSH + Cordis Is Different

Build and publish

Plugin HMR Not WorkingPlugin Not Showing Up After Publishing

Troubleshooting

Troubleshooting Plugin Install FailuresDSH Version IncompatibilityResolve ERR_PNPM_IGNORED_BUILDSTroubleshoot Cordis Startup FailuresPreset Not Found or Cannot Be ResolvedTroubleshoot a Blank DSH Web UIlocalhost:3080 Is Unreachable
Plugin Hub/Documentation/Get started

Get started

Write Your First DSH Plugin

The complete workflow from scaffolding to publishing: init, validate, publish, claim.

Maintained by the Plugin Hub community5 sections
What you will learn

The complete workflow from scaffolding to publishing: init, validate, publish, claim.

Initialize the project

Use the CLI to generate a complete plugin scaffold:

bash
dsh-hub init my-plugin --repository your-name/my-plugin

# With a scoped package name
dsh-hub init my-plugin --name @your-scope/my-plugin --repository your-name/my-plugin

Project structure

The generated project contains three core files:

package.json — contains npm metadata and the DSH manifest (dsh.bundle, hub listing info, compatibility declarations).

cordis.patch.yml — defines the plugin's Cordis entries, describing how the plugin registers itself in the system.

src/ — the plugin source code directory.

Validate locally

Before publishing, check all format requirements with the validate command:

bash
dsh-hub validate my-plugin

Publish to npm

After validation passes, publish like a normal npm package:

bash
cd my-plugin
npm publish

Appearing on the Hub

After publishing, the plugin will appear automatically in the next hourly sync cycle. You can also manually submit the package name on the plugins page for faster discovery.

To manage listing info (screenshots, categories, description), claim your plugin: sign in to the Hub, install the GitHub App on your repository, and after verification you can edit directly in the Dashboard.

Continue reading

Continue reading

Get startedDistribute a Carefully Tuned Agent Harness with PresetsPresets turn a carefully tuned Agent Harness into a shareable, verifiable, rollback-ready Release that others can use without learning how it was assembled.ArchitectureThe Cordis Plugin Model Behind DSHUnderstand how Context, services, injection, and reversible effects let DSH assemble an entire Agent Harness as a plugin tree.ArchitectureFrom a Service to a Complete Agent CapabilitySee how DSH combines service definitions, providers, consumers, events, and scopes into complete replaceable capabilities.

On this page

OverviewInitialize the projectProject structureValidate locallyPublish to npmAppearing on the Hub