Topic
dsh-plugin
github.com/topics/dsh-plugin
Community
dsh-plugin on GitHub find DeepSeek Harness community plugins
Browse breadth on GitHub topics, then validate README, secrets scope, and disposers before Standard. Prefer curated cards when you want rewritten, locale-aware notes.
- Topic ≠ security audit
- README before install
- Unload must work
Audit
Maintainers
Scope + secrets + disposer
Modes
Test first
Minimal / Creative before Standard
Curated
On-site list
/plugins/directory/
What the dsh-plugin topic is good for
Browse github.com/topics/dsh-plugin when you want breadth: new tools, skins, providers, and experiments. Authors should add the topic only when the repo is meant for discovery — see contribute. A topic tag is a discovery signal, not a security review, not a DeepSeek endorsement, and not a substitute for reading the README.
Topic membership does not mean DeepSeek reviewed the code. It does not mean this portal endorses the package. Read the README for secrets, filesystem scope, and uninstall steps. Prefer dsh plugin add github:owner/repo lines you can audit. Test in Minimal or Creative before Standard — modes. Watch Trajectory after each add so you can unload the last package when something smells wrong.
The plugin guide assumes you can reverse an add. If a package cannot explain disposer behavior, skip it. This site’s curated community plugins list rewrites cards slowly on purpose — use curated when you want locale-aware notes, and the topic when you knowingly want the long tail. Stabilize core flows via install first.
Why discovery needs discipline
Firehose ≠ endorsement
Topic tags are discovery signals. Security and quality remain your homework.
Blast radius is real
Plugins can touch files and shell. Narrow workspaces and careful modes matter.
Curated latency is intentional
We will not scrape thousands of thin pages. Use curated as navigator; topic as long tail.
Publish with honesty
Document secrets and uninstall before asking for discovery — [contribute](/en/contribute/).
Discover without getting burned
-
1
Stabilize core flows
Install via [install](/en/install/) and confirm [Web UI](/en/dsh/web-ui-guide/) before any community add.
-
2
Prefer curated, then topic
Start at [plugins/directory](/en/plugins/directory/). Open the topic when you knowingly want more surface area.
-
3
Audit README + maintainer
Check scopes, secrets, disposer. Follow [plugin guide](/en/plugins/guide/).
-
4
Add one package at a time
Test in Minimal/Creative ([modes](/en/modes/)). If the UI breaks, unload and use [troubleshoot](/en/troubleshoot/).
Go deeper
GitHub projects tagged dsh-plugin — check maintainers and code quality before use.
Maintainer checks before you install
Prefer packages you would run as software even without an agent. Check recent commits, issue hygiene, and whether uninstall is documented. Compare community awesome-lists on code-directory. Architecture context: architecture. Cordis habits: cordis.
Curated directory vs topic firehose
Curated cards are rewritten and locale-aware; the topic stays wider and faster-moving. Product entry: overview. Hub home for sibling spokes: DSH resources. Neither list is a sandbox — modes and workspace roots still matter.
After you pick a package
Confirm the Web UI via web-ui-guide, add one package, watch Trajectory. Chapter form: tutorials. npm identity if launch fails: npm. Source truth: github. Port or process noise: troubleshoot.
Publishing under the topic
Ship a package, document secrets and disposers, add the topic, then read contribute for publish norms on this portal. Site FAQ for “is this DeepSeek HQ?” questions: FAQ.
FAQ
Is every dsh-plugin topic repo safe?
No. Treat them like any GitHub software. Verify maintainers and scopes; follow the plugin guide and test in careful modes.
Where is the curated list on this site?
At plugins/directory. It is narrower and rewritten; the topic stays wider.
How do I publish under the topic?
Ship a package, document secrets, add the topic, and read contribute.
What if a plugin breaks the UI?
Unload it, then check troubleshoot for port and process issues unrelated to the package.
Does this topic page mean harness-ds.com is DeepSeek HQ?
No. We map discovery and safety. Product framing is on deepseek.com/harness; see FAQ.
Discovery without curation is homework. Start from the curated directory when you can; use the topic when you knowingly want more surface area — and still read the README.
More curated DSH resources
Each card opens a full landing page — same hub, different job.
- DSH Official
DeepSeek Harness
Official introduction and entry for the DeepSeek Harness developer preview.
Open resource ↗ - GH Official
deepseek-ai/deepseek-harness
Official MIT open-source repository with source, examples, contribution history, and releases.
Open resource ↗ - npm Official
@deepseek-ai/dsh
Official @deepseek-ai/dsh npm package for launching the local Web UI.
Open resource ↗ - UI Official
DSH Web UI Guide
Official getting-started notes: configure a model, pick a workspace, run the first task.
Open resource ↗ - DOC Official
DSH Architecture
Technical docs on Cordis, plugins, services, session state, and the Agent Loop.
Open resource ↗ - CO Independent community
Cordis
Spatiotemporal composition framework and plugin service model underneath DSH.
Open resource ↗ - DIR Independent community
DeepSeek Code Directory
Independent community directory of DSH plugins, tools, and infrastructure by category.
Open resource ↗
Plugin discovery next steps
Read the plugin guide, compare the community code directory spoke, or install DSH before adding packages.