DeepSeek Harness Plugin Hub

Troubleshooting

Profile 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

Confirm the three names

The first argument is the Hub Profile 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 Profiles 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

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.