Discover reviewed DeepSeek Harness extensions, compare what they add, inspect their public source and README notes, and start from an installation command grounded in the maintainer’s documentation.
Curated directory
Search the first reviewed collection by capability, project name, or installation format.
16 of 16 plugins
DSH 上下文注入审计插件：统计 AGENTS.md 指令链/技能目录/工具 schema 的 token 成本，检测重复与冲突；Web UI 圆环面板 + context_audit 工具。Context Doctor for DeepSeek Harness: audit instruction-chain / skill catalog / tool schemas token cost.
npx -y @deepseek-ai/dsh plugin --profile web add dsh-context-doctorVerified for DSH Plugins
dsh plugin: Chrome sidebar extension that lets DSH operate your browser directly—no vision capabilities required.
npx -y @deepseek-ai/dsh plugin --profile web add /absolute/path/to/dsh-browserVerified for DSH Plugins
Plugin and skin collection for DeepSeek Harness (DSH) Web UI - task board, git graph, right-side panel, remote mobile UI, pet, live token stats, and skin center.
npx -y @deepseek-ai/dsh plugin --profile web add /absolute/path/to/dsh-web-uiVerified for DSH Plugins
dsh-tianshu-tui — DeepSeek Harness terminal UI
npx -y @deepseek-ai/dsh plugin --profile tui add @huiliyi37/dsh-tianshu-tuiVerified for DSH Plugins
A VS Code-inspired DSH workspace sidebar with files, terminal, Git, subagents, and extension tabs.
dsh plugin --profile web add link:/absolute/path/to/DSH-better-sidebarVerified for DSH Plugins
Native visual engineering tools for DSH agents, including image Q&A, OCR, grounding, cropping, pixel diff, and UI restoration.
dsh plugin --profile web add "$PLUGIN"Verified for DSH Plugins
Coordinate persistent DSH subagents as a team with roles, dependencies, direct messages, and live activity.
npx -p @deepseek-ai/dsh dsh plugin --profile web add github:NanmiCoder/dsh-agent-teamsVerified for DSH Plugins
Codex-style @file mentions for DeepSeek Harness, with bounded workspace search and prompt-safe file attachment.
dsh plugin --profile web add file:/path/to/dsh-at-fileVerified for DSH Plugins
Accessibility-first macOS computer control for DSH with fresh observations and scoped, confirmed actions.
dsh plugin --profile web add "$PLUGIN"Verified for DSH Plugins
Create and manage sandboxed JavaScript tools in DSH with schema validation, limits, and a Monaco editor.
dsh plugin --profile web add file:/path/to/dsh-custom-toolVerified for DSH Plugins
Edit, reroll, and retry DSH messages through branch-based versions without rewriting session history.
dsh plugin --profile web add -w link:/absolute/path/to/dsh-message-editVerified for DSH Plugins
Desktop notifications for DSH turn outcomes with per-status and keyword include or exclude controls.
dsh plugin --profile web add file:/path/to/dsh-notificationVerified for DSH Plugins
Open a DSH workspace in VS Code directly from the Web interface with a user-initiated menu action.
dsh plugin --profile web add file:/path/to/dsh-open-in-vscodeVerified for DSH Plugins
Share DSH conversations through a focused export interface with readable layout and display controls.
dsh plugin --profile web add --ignore-scripts --config.auto-install-peers=false github:hellodigua/dsh-share#v0.1.0Verified for DSH Plugins
Rewind DSH conversations and workspace state through append-only branches and a persistent change ledger.
dsh plugin --profile web add /path/to/dsh-turn-rewindVerified for DSH Plugins
Render interactive, sandboxed HTML visualizations directly inside the DSH conversation stream.
dsh plugin --profile web add link:/path/to/dsh-visualizeVerified for DSH Plugins
A useful directory, not a dump
DeepSeek Harness is designed around composition: tools, services, interface surfaces, and agent behavior can arrive as plugins instead of permanent core patches. That flexibility is powerful, but discovery becomes harder as the ecosystem grows. DSH Plugins gives developers one clear place to compare public projects, understand what each extension changes, and reach the original source before installing anything.
DSH Plugins keeps concise summaries beside searchable names, so you can move from a problem to a relevant project without scanning topic pages and unrelated repositories.
DSH Plugins checks the repository state, installation documentation, and listing quality before a submission becomes public. Review is a quality signal, not a security warranty.
DSH Plugins distinguishes package targets from local checkouts and preserves upstream notes when a plugin needs a build, a restart, profile-specific setup, or an extra Cordis row.
From source to profile
DSH Plugins does not install software on your machine. It helps you inspect a project, understand the documented path, and copy an appropriate starting command. You remain in control of the checkout, package manager, profile, credentials, and permissions.
Search DSH Plugins by project name, capability, or installation type. Every public result has passed the directory review queue.
Open the detail page, read the concise explanation, follow the source link, and compare the saved README notes with the current upstream repository.
Copy the command as a starting point, replace local paths when needed, use the profile you actually intend to change, and restart long-running DSH processes when the plugin instructs you to.
Confirm the bundle appears in the composed profile, check settings or tool surfaces, and remove the dependency if the plugin does not behave as expected.
Start with the job you need to improve. Some DSH Plugins add a narrow action, such as opening a workspace in an editor or notifying you when a turn finishes. Other DSH Plugins introduce a complete work surface, a group of model tools, or a stateful workflow. A focused plugin is often easier to review and remove, while a broad bundle may be the right choice when its capabilities share configuration and lifecycle requirements. The directory summary tells you the intended boundary; the repository tells you how that boundary is implemented.
Pay close attention to where code runs. Browser-only DSH Plugins may change presentation without granting a model any new tool. Host-side DSH Plugins can read settings, register services, expose endpoints, or interact with the workspace. Agent-facing DSH Plugins may make additional schemas visible to a model. None of those categories is automatically good or bad, but they carry different review questions. Look for explicit dependency declarations, bounded inputs, reversible registration, and a clear explanation of files, credentials, network calls, or native permissions.
Installation format matters too. Registry-ready DSH Plugins can be added through a package spec, while many early ecosystem projects are distributed as local checkouts with committed build output. A local install is not inherently less trustworthy; it simply asks you to manage the source directory and updates yourself. Check whether the README says to run a build, whether `lib` artifacts are committed, whether `file:` or `link:` semantics are expected, and whether a profile restart is necessary. DSH Plugins preserves those differences instead of reducing every project to a misleading one-line command.
Finally, check maintenance signals. Useful DSH Plugins explain supported Harness versions, operating-system requirements, known limits, upgrade steps, and uninstall behavior. Tests and reproducible verification are stronger evidence than a badge alone. Recent commits can help, but a small stable plugin may not need frequent changes. DSH Plugins therefore avoids a simplistic popularity ranking: the goal is to make primary evidence easy to reach so you can decide what fits your environment.
DSH Plugins helps maintainers present a stable explanation outside a fast-moving repository feed. Submit the canonical GitHub URL, choose the installation format, and add a short summary if the repository description needs context. DSH Plugins imports the public metadata and README into a pending record; an administrator checks the listing before publication.
Submit to DSH PluginsNew DSH Plugins submissions are not published immediately. The service first rejects URLs that are not canonical public GitHub repositories, along with repositories GitHub marks private, archived, or disabled. It then stores a bounded README snapshot and the repository’s default branch. This protects DSH Plugins from arbitrary server-side fetches and prevents the public catalog from becoming an unreviewed mirror of every topic result.
A human administrator checks the proposed name, summary, installation type, and target. The reviewer can refresh metadata, correct a record, approve it, or reject it with an internal reason. Approved DSH Plugins receive a publication time and become eligible for the homepage, plugin detail routes, structured data, and sitemap. Rejected DSH Plugins stay private and can be resubmitted by the original contributor after changes.
DeepSeek Harness uses Cordis composition so capabilities can register and unwind with plugin lifecycle. That makes DSH Plugins more than cosmetic add-ons. One extension might provide a service consumed by another; one might add a browser contribution paired with a Host remote; another might publish a Skill that progressively exposes tools only when an agent needs them. Reading the architecture section of a repository helps you understand whether the plugin belongs in Web, Headless, or both profiles.
The first DSH Plugins collection deliberately mixes small interface improvements and larger agent capabilities. It shows how broad the extension model can be without pretending every visitor wants the same stack. You can add file mentions without adopting a complete workspace sidebar, add notifications without exposing a model tool, or install visual and computer-use bundles only in profiles where their permissions make sense. DSH Plugins supports that selective approach by keeping every listing independent.
The GitHub `dsh-plugin` topic remains an important open discovery source, and DSH Plugins links back to it. The difference is editorial control. A topic can include experiments, adjacent projects, abandoned repositories, or items whose relationship to Harness is not immediately clear. DSH Plugins starts smaller so every public page can explain what the project is, where it comes from, and how its maintainer says it should be installed. More DSH Plugins can be added through the same review path as maintainers improve documentation.
DSH Plugins is English-first in this release to keep metadata, summaries, legal pages, and review language consistent. Repositories may use any language, and saved README content remains in the author’s original language. The directory does not rewrite technical claims or claim ownership of upstream documentation. If the DSH Plugins summary and the current repository diverge, treat the upstream source as authoritative and report the outdated listing to the contact address in the footer.
Questions before you install
DSH Plugins are extension packages for DeepSeek Harness. They can add model tools, services, settings, interface panels, workflow behavior, or complete profile bundles without requiring every capability to live in the Harness core.
Every submission enters a pending queue. An administrator checks that the GitHub repository is public and active, reads the documented installation path, reviews the summary and README snapshot, and publishes only after the directory record is accurate.
No. Review improves directory quality, but third-party software can change and may request powerful capabilities. Read the source, inspect permissions and dependencies, pin a version when possible, and test unfamiliar plugins in a profile you can restore.
Each listing preserves its reviewed target profile and full installation command. Web and headless are built-in templates; names such as tui are custom profiles initialized from dsh-base. Always follow the upstream README because some projects require npx, extra flags, a build, or additional configuration.
A local listing is installed from a cloned checkout rather than a published registry package. This is common while the DSH ecosystem moves quickly. Local installation also lets developers inspect or build the exact source before adding it to a profile.
No. The first release accepts public GitHub repositories only, because reviewers and directory visitors need to inspect the source and README. Archived and disabled repositories are also rejected automatically.
DSH Plugins is an independent community directory. DeepSeek Harness, listed plugins, trademarks, and repository content remain the property of their respective maintainers.
For now, contact the directory team or submit the same repository again after a rejection. Approved duplicates are blocked to protect canonical URLs. A broader maintainer dashboard is intentionally outside the first release.
