The dsh Ecosystem: Packages, Community Lists & GitHub Topic

A map of the DeepSeek Harness (dsh) ecosystem: the official repo and npm package, community catalogs this directory aggregates, and the dsh-plugin GitHub topic.

Last updated: 2026-08-18

The official anchors

The ecosystem starts with three official touchpoints:

Repo — deepseek-ai/deepseek-harness — "DeepSeek Harness: Everything is a Plugin." Open source, MIT-licensed, TypeScript.
npm — @deepseek-ai/dsh — the CLI. npm install -g @deepseek-ai/dsh then dsh --profile web launches the Web UI.
Topic — dsh-plugin — the official GitHub topic for community plugins. Adding this topic to your repo is the single most effective way to be discovered.

The project is at v0.1, explicitly aimed at harness developers, with core plugins and interfaces expected to iterate quickly.

The list this directory is built from

This site has a single source of truth — our own awesome list:

cccakeee/awesome-dsh-plugins

Every plugin page on this site is one line in that README. The list follows the awesome-list convention (a category heading, then - [name](url) — description per plugin), and both English and Chinese section headings are recognized. PRs are welcome — see how to submit.

The dsh-plugin topic (for discovery elsewhere)

GitHub's dsh-plugin topic is the official community marker for DeepSeek Harness plugins. We recommend every plugin repo carries it — other tools and directories discover plugins through it. It does not feed this directory (which only reads our list), but it's how the wider ecosystem finds you.

Category taxonomy

Every entry sits in one of 22 first-class categories, each with its own landing page in this directory:

UI & Experience — skins, sidebars, panels, terminal UIs
Sessions & Messages — message editing, sharing, conversation navigation
Agents, Automation & Workflows — loops, sentinels, multi-agent orchestration, workflows
Integrations & Sharing — notifications, bridges, sub-agents, sharing
Developer Tools — plugin health checks, audits, diagnostics, sandbox backends
Knowledge & Research — memory, search, document parsing, research agents
Design, Media & Vision — vision toolkits, OCR, image generation, design canvases
Web & Browser — browser automation, web search, web content agents
Desktop & Apps — Electron wrappers, tray apps, editor extensions
MCP & Protocols — MCP servers and protocol bridges
Plugin Tooling — plugin managers, templates, verifiers, bundlers
Web UI & Frontend — web UI panels and frontend components
Themes & Skins — visual themes and color schemes
Security & Auth — authentication, permission policies, guards
Chat & IM — WeChat, Telegram, Discord and other chat bridges
CLI & Terminal — TUI dashboards, headless runners, shell helpers
Voice & Speech — text-to-speech, speech-to-text, voice input
Lists & Resources — curated lists and awesome-list mirrors
Usage & Billing — token trackers, cost dashboards, balance alerts
Ecosystem & Resources — registries, skill packs, lists themselves
Just for Fun — pets, mini-games, stickers, parody ads
Other — the catch-all for everything not yet themed

Entries that would land in the catch-all are re-mapped at load time into the themed categories above based on their GitHub topics and descriptions, so the themed pages stay populated.

How this directory stays fresh

The catalog is served from a committed snapshot (src/data/plugins.snapshot.json) that is bundled into the build — rendering the directory makes no network calls, so the site never goes dark.
Running pnpm sync:plugins re-fetches our list (plus the temporary bootstrap sources), re-parses every entry and regenerates the snapshot; committing the result refreshes the catalog on the next deploy.
Plugin detail pages are the exception: each repo's README is fetched on demand from GitHub and cached for 24 hours, so detail content stays current without a rebuild.

You can rebuild the snapshot locally with:

pnpm tsx scripts/sync-plugins.ts

Safety notes

Listing is not endorsement. Nobody audits third-party plugins here; the list itself says so.
Check the plugin repo before installing — read its README, license and what it accesses.
Prefer isolated workspaces and the harness's sandbox tiers (read-only → workspace-write) when trying something new.
Not affiliated with DeepSeek. This is an independent community directory.