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/Troubleshooting

Troubleshooting

Preset Not Found or Cannot Be Resolved

Distinguish Hub slugs, Release versions, and local Profile names to restore a reproducible apply flow.

Maintained by the Plugin Hub community2 sections
What you will learn

Distinguish Hub slugs, Release versions, and local Profile names to restore a reproducible apply flow.

Confirm the three names

The first argument is the Hub Preset slug, --version selects a published Release, and --profile names the local DSH Profile directory. The three values may differ. Search first and copy the slug shown in the detail response.

bash
dsh-hub profile search <keyword>
dsh-hub profile show <profile-slug>

Check visibility, version, and API

Private Presets and unpublished drafts do not appear in public search. If an explicit version returns 404, inspect the Release list and letter case. When HUB_API_ORIGIN is set, confirm it points to the same Hub environment. Resolve with a dry run, then verify local state with doctor.

bash
dsh-hub profile apply <profile-slug> --version <exact-version> --profile web --dry-run
dsh-hub profile doctor <profile-slug> --version <exact-version> --profile web

Continue reading

Continue reading

TroubleshootingTroubleshooting Plugin Install FailuresGetting errors when installing a plugin? Follow this checklist to diagnose package name, manifest, version format, and network issues.TroubleshootingDSH Version IncompatibilityHow to diagnose and fix version range mismatches between a plugin's declared compatibility and your DSH environment.TroubleshootingResolve ERR_PNPM_IGNORED_BUILDSReview dependency build scripts blocked by pnpm and approve only the packages required for installation.

On this page

OverviewConfirm the three namesCheck visibility, version, and API