DeepSeek Harness Plugin Hub

Troubleshooting

Troubleshoot Cordis Startup Failures

Trace DSH startup errors through Profile integrity, Bundle order, and service dependencies.

Maintained by the Plugin Hub community2 sections

Check before startup

Run doctor first. It reports a missing package.json, cordis.patch.yml, lockfile, Bundle, or required input before Cordis starts. Then use diff to inspect additions, removals, versions, sources, and load-order changes.

bash
dsh-hub profile doctor --profile web --json
dsh-hub profile diff <profile-slug> --version <version> --profile web

Find the earliest failing service

Keep the complete startup output and find the first missing-service, duplicate-entry, or configuration-validation error. Check the row's injected dependencies and whether its Provider is in the active Context. If an upgrade introduced the failure, restore a known-good revision from history.

bash
dsh-hub profile history --profile web
dsh-hub profile rollback <revision> --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.