Plugin Development

Start by cloning deepseek-harness and learning how a DSH-Plugin installed into a profile is managed by pnpm while dsh plugin forwards commands; debug in an isolated profile and verify loading with dsh --dump-config.

This category is for developers extending the DeepSeek Harness Plugin (DSH plugin) ecosystem: project structure, dev environment, and debugging, plus how to add a new plugin to a profile, verify loading with dsh --dump-config and why, and follow official examples. Develop in an isolated profile so your daily web environment stays stable.

DSH-Plugin tutorial list

DSH plugin development FAQ

What environment do I need to develop a DSH plugin?

The same as using DSH — Node.js and pnpm. Clone the official deepseek-harness repo for reference and set up a separate profile for debugging.

How do dsh plugin and pnpm relate?

Everything after dsh plugin --profile <name> is forwarded verbatim to the pnpm inside that profile's directory — like running pnpm under ~/.dsh/profiles/<name>, so the action word goes last.

How do I verify my plugin loads correctly?

After installing, inspect the config tree with dsh --dump-config, confirm dependencies with dsh plugin --profile <name> why <package>, then launch dsh web to see the capabilities appear.

How do I keep development from interfering with daily use?

Create a separate profile (e.g. --profile dev) and install the in-development DSH plugin there; your daily web profile stays stable and the two do not interfere.

Are there official examples to follow?

Yes. The deepseek-ai/deepseek-harness repo's apps directory contains official implementations, and plugin detail pages on dsh-plugin.org list install commands and repo links.