Developer plugins for DeepSeek Harness
Build, debug and operate the harness and its plugins.
Development plugins are for people who build on the harness or keep an instance of it running. They include scaffolding for new plugins, inspectors that show what is loaded and what events are passing through, log and trace viewers, and helpers for deployment and health checks. Most users will never need them; plugin authors and operators will use them constantly.
1 plugin
How to choose
Match the plugin to the harness version you run, because tooling that reaches into internals is the first thing to break during a developer preview. Debugging tools often expose prompts, keys and internal state, so keep them out of any instance that other people can reach. For scaffolding, generate a project and read the result: it should be small enough that you understand every file.
Terms used on this page
- Hot reload
- Applying a code change to a running plugin without restarting the whole harness.
- Trace
- A recorded sequence of events, model calls and tool calls for one run, used to work out what happened.
- Scaffold
- A generated starting project with the minimum files and settings a new plugin needs.
Questions and answers
Should I leave debugging plugins enabled in everyday use?
Better not. They add overhead, and some of them reveal data you would not want exposed. Turn them on when you are investigating something and off again afterwards.
Do I need these plugins to write my own plugin?
No. A plugin is ordinary code and can be written with the tools you already have. Development plugins shorten the edit and test loop and make problems easier to see, which starts to matter as your plugin grows.