Directory live · Developer preview v0.1 · Everything is a plugin
300+ plugins appeared in days of private beta—with no catalog. This site lists only repos you can verify on GitHub: pick a category, scan this week's ten, then choose one to install.
Why this site exists
DeepSeek Harness is built on Everything is a plugin: models, tools, skills, sessions, sandboxes, storage, loops, scheduling, and UI are all Cordis plugins. The meta-framework only loads, unloads, and resolves dependencies; real Agent capability is assembled from plugins. You can swap any piece without patching Harness source.
That's freedom for veterans and noise for someone who just ran `npx @deepseek-ai/dsh web`. Settings can install packages, but won't tell you whether the sidebar should be DSH-better-sidebar or dsh-web-ui, whether memory should be dsh-memory-evolve or dsh-mnemon, or that make-dsh-plugin in plugin-registry is the right starting point. Three hundred names sit flat under topic tags—no categories, no install order, no "skip this one first."
This site is that map. Five categories by intent: UI, long-term memory, tools, efficiency, and development. Every name comes from public repos and awesome-deepseek-harness—nothing invented. Install commands follow each repo's README. To run Harness itself first, see the install guide at deepseekharness.xyz.
Pick by intent
Updated weekly
This week · 2026 week 33. Updated around new plugins and public repo activity. Rankings are not download counts (there is no public store yet)—they are the ten READMEs most worth reading when you first touch DSH. Bind to a preset copy before enabling; don't turn on ten globally at once.
Install first, ecosystem second
01
On the web profile, add a GitHub source to the bundle stack or an insert line. Restart `dsh web` after bundle installs; wait for config HMR on pure cordis.
dsh plugin --profile web add "github:owner/repo" # Subpath (e.g. plugin-registry console): dsh plugin --profile web add "github:vlln/plugin-registry#main&path:/packages/plugin/console"
02
After official 0811, external plugins all go through the web profile. The settings plugin panel shows the insert zone (live mount) and bundle zone (restart to apply). plugin-registry's thin console draws both.
03
Clone, build, then `dsh plugin --profile web add link:/absolute/path`. Hard-refresh if UI doesn't appear; Node half changes need a process restart.
Read next
Plugins can change tool allowlists, system prompts, and UI mount slots—so the security model is not Chrome extensions. Presets decide what the current session sees; profiles decide what loads at process start. The compare page and FAQ explain that together.