Develop
Creation mode (cordis) lets you inspect runtime and trial plugins in memory. These repos are scaffolds for writing plugins—not daily coding sessions.
plugin-registry pivoted in 2026-08 to a thin console plus conventions. Official 0809 repo plugins covered ~95% of the old standalone mechanism; repository-plugins was removed 0811. External plugins only via web profile: bundles into `dsh.profile.bundles`, pure cordis via `cordis.patch.yml` insert. The console draws both zones in settings. The bundled make-dsh-plugin skill walks skill / MCP / Node tool / UI shapes and `dsh.bundle` or pure apply.
oh-my-dsh rewrites capabilities from other open Harnesses (OpenCode, Claude Code, Codex, pi, etc.) as DSH plugins—only via `ctx.effect()` / `ctx.on()` / `ctx.tools`, never patching agent-loop. README cites 687 plugins and green tests—treat as reference implementations and templates, not six hundred inserts into production profile. dsh-plugin-check catches manifest, patch format, build traps, and hub status before you publish.
marisa is an external plugin manager (parasitic install / CLI / settings panel). turtle-ui is the official UI reference when writing the client half. dsh-inspect runs adversarial check→fix→review loops—quality engineering. awesome's hub repo CI-generates catalog.json; this site's weekly list follows that public index, not closed beta screenshots.
Publishing: tag `dsh-plugin` and `deepseek-harness`, README must state profile, restart vs HMR, and permissions. Private beta #dsh tags were a migration convention—public repos under personal accounts for discovery. Full steps in the developer guide.