Write a DeepSeek Harness plugin (dsh-plugin)

Official slogan: everything is a plugin. Models, tools, skills, sessions, sandboxes, storage, loops, scheduling, and the UI sit on the Cordis kernel. A DeepSeek Harness plugin is a Cordis component, not a Claude “skill.md”.

Before you write one

1. Run DSH from source, not only npx. You will read docs/ (architecture, cordis-primer, capability-seams).
2. Open Creator mode. It can inspect the live runtime and load an in-memory plugin. Those plugins die on restart today.
3. Read CONTRIBUTING.md and AGENTS.md in the official repo.

This page is a map, not a substitute for those files. APIs will move.

What a useful first plugin is

Pick a hole the official Web UI left open:

• TUI / desktop window
• Browser or Feishu / Lark bridge
• Safer delete, token meter, VS Code jump
• Search provider swap

See what already exists on the plugin list. Do not clone another directory.

Publish

1. Ship a real install path (pnpm / npx / copy into plugins dir — whatever the current official docs say).
2. Add the GitHub topic dsh-plugin.
3. Write which DSH commit you tested. Preview builds break weekly.

Creator mode vs a real plugin

Creator mode is for experiments. A dsh-plugin repo is for something that survives a reboot. If your feature only exists in RAM, it is not a plugin yet.