DeepSeek Harness (dsh) Starter Plugin Template

AI-generated setup and plugin-scaffold checklist referring to DeepSeek Harness and Cordis. Check linked upstream instructions; compatibility and commands are not verified here.

Tags: plugin, deepseek, deepseek-harness, dsh, cordis, agent-runtime

Category: coding

Listing attribution: SimplyUtils

Before using this resource

Attribution and license labels come from the listing metadata. Check the source and its license before redistributing or adapting files. This listing has no documented license; do not assume permission to redistribute it.

Read instructions before adding them to an agent or project. Test a small, non-confidential example and inspect the result. A downloaded instruction file may refer to scripts, templates, or other files that are not included here.

SimplyUtils supplied this template, which was generated by an AI agent using an LLM. It is an example to inspect and adapt, not a verified package or a record of expert testing. Check named dependencies, commands, permissions and generated results before use. Redistribution terms for this template have not been verified; licenses for third-party software are separate.

Source

Repository

DeepSeek Harness (dsh) Starter Plugin Template

What is DeepSeek Harness?

DeepSeek Harness (dsh) is an open-source agent harness built by DeepSeek AI. It runs as a local CLI/Web UI (npx @deepseek-ai/dsh web, default at http://127.0.0.1:3080) and is architected so that everything is a plugin, powered by Cordis, a spatiotemporal-composability framework.

> ⚠️ dsh is in developer preview — expect breaking changes between releases. Always check the current architecture docs and development guide before relying on a specific plugin API shape.

Local setup

git clone https://github.com/deepseek-ai/deepseek-harness.git
cd deepseek-harness
pnpm install
pnpm run build
pnpm dsh web --no-open

Plugin scaffold checklist

1. Isolate your plugin as its own package (own package.json, own tsconfig) so it can be versioned and published independently of the harness core.

2. Register through the Cordis context (ctx) — Cordis plugins compose behavior by attaching to a shared context object rather than importing globals directly. Confirm the exact registration call (ctx.plugin(...) or the current equivalent) against the primer linked in the Cordis repo, since the API is still evolving.

3. Declare capabilities explicitly — list the filesystem, network, or MCP permissions your plugin needs so users can audit it before installing, matching how this catalogue tracks permissions.

4. Tag it for discovery — add the dsh-plugin topic to your plugin's GitHub repo so it surfaces in github.com/topics/dsh-plugin.

5. Write an AGENTS.md note — DSH's own repo documents agent-facing contracts in AGENTS.md; mirroring that convention in your plugin repo helps coding agents use it correctly.

Where to get help

Why add this to SimplyUtils

DSH is brand new and rapidly changing, so a lightweight, honestly-scoped starter checklist is more useful right now than a rigid code template that will drift out of date — link out to the primary sources instead of re-deriving unstable internals.