DeepSeek Harness Plugins: The 616+ Community Extension Ecosystem

DeepSeek Harness is built around one idea: everything is a plugin. The Cordis kernel only mounts, unmounts, and resolves plugin dependencies — every agent capability lives in plugins: models, tools, skills, sessions, sandboxes, storage, loops, scheduling, and the UI^[1].

That is why the plugin ecosystem exploded within days of the August 13, 2026 launch. Three days in, the community index listed 616 plugins, the official awesome-dsh-plugin list passed 4,519 stars, and the main repository passed 127,689 stars^[2].

You do not fork the harness to change behavior; you install or write a plugin. Capabilities are composed in configuration, and swapping one plugin is a config change, not a source change^[1].

• Models and providers are plugins (dsh-llm-pi-ai, dsh-llm-deepseek)
• Tools, skills, sandboxes, and sessions are plugins
• Even the agent loop, scheduling, and the UI are plugins

Plugins are npm packages with a dsh.bundle manifest. Install them per profile with dsh plugin, which forwards to pnpm^[2].

For publishers: add the dsh-plugin topic to your GitHub repo so the ecosystem lists discover it. The official recommendation for extending dsh is to publish a plugin rather than patch the source^[2].

The plugin model also means the harness UI itself is extensible: the desktop shell (deepseek-harness-desktop), the Web UI skin with task board and git graph (dsh-web-ui), and the Claude Code-style TUI (dsh-TUI) are all plugins you can stack on the same profile^[3].

# Install a plugin into the web profile
dsh plugin --profile web add <package-name>

# Install the community plugin market, then browse it
dsh plugin --profile web add dshmarket

# Chat-based plugin finder
dsh plugin --profile web add dsh-find-plugin

# Add a plugin to a headless/other profile the same way
dsh plugin --profile headless add <package-name>

Three discovery channels cover the ecosystem in August 2026^[2].

Because the main repo has GitHub Issues disabled and accepts no external PRs, contribution happens through plugin publication and GitHub Discussions — which is exactly why the plugin channel is the growth surface^[2].

• awesome-dsh-plugin (official community list, 4,519★) — categorized: UI, Models & Providers, Sessions & Messages, Memory, Tools, Vision, Skills, Workflow, Notifications, Dev & Runtime, Plugin Markets
• deepseekharness.io — community index tracking 616 plugins
• dshmarket — the in-app plugin market you install with dsh plugin add dshmarket

Star counts as of August 16, 2026 — momentum indicators in the launch window^[2].

Installing a plugin means running third-party code on your machine, with access to your files, credentials, and network^[2].

The community's own security warning is blunt: tool approval does not sandbox plugin code. A plugin can read your files, use your stored API keys, and reach the network. Review unfamiliar plugins — read the source, check the stars and recency — before adding them to a profile that holds credentials^[2].

Recommended practice: test new plugins in a clean profile with no keys stored, then promote them to your working profile only after they behave.

Building your own stack on top of the plugin model? The Cordis architecture guide explains how plugins mount and compose, and the full tutorial walks through a plugin-backed agent setup end to end.

• Install unfamiliar plugins into a credential-free profile first
• Prefer plugins from the official awesome list or with visible source
• Remember keys are stored in $DSH_HOME/.credentials.yaml and written-only