DSH, plugins, and this directory.

DeepSeek Harness is an open-source agent harness developed by DeepSeek AI. It provides the runtime around an agent—models, tools, sessions, filesystems, sandboxes, orchestration, and interfaces—while keeping those capabilities replaceable.

The official source and documentation live in the deepseek-ai/deepseek-harness repository.

DSH is powered by Cordis. Plugins contribute services, typed events, and reversible effects to a shared context. Even the model adapter, tool registry, session log, and agent loop are plugins, so behavior is composed through configuration rather than by patching a privileged core.

Replaceable does not mean interchangeable without review; plugins still have versions, contracts, permissions, and compatibility constraints.

Run the official Web profile with npx. DSH is currently a developer preview and explicitly expects compatibility-breaking changes, so pin versions for repeatable environments and review release notes before updating.

npx @deepseek-ai/dsh web

The Web UI is served at http://127.0.0.1:3080 by default.

A plugin is a mounted extension that contributes behavior to the shared Cordis context. It can provide or consume capabilities such as models, tools, memory, filesystems, sandboxes, orchestration, or UI. An npm package may contain one plugin, multiple plugins, or a bundle that mounts a configured set.

The package README and manifest—not its name alone—define what it actually contributes.

A plugin contributes runtime behavior. A bundle distributes ordered Cordis configuration rows and the code they mount. A profile is a named composition stored in DSH home: it stacks bundles, owns installed out-of-tree dependencies, and keeps the user's cordis.patch.yml.

npx @deepseek-ai/dsh --profile web --dump-config

The profile determines where a plugin is installed and which application composition receives it.

Use the profile-scoped plugin command. DSH initializes the selected profile on first use, forwards the operation to pnpm inside that profile, then reconciles installed packages that export DSH bundles.

npx @deepseek-ai/dsh plugin --profile web add <package>
npx @deepseek-ai/dsh plugin --profile web remove <package>

Restart the running profile after changing its dependency stack.

No. A package that declares dsh.bundle.patch can join the profile layer stack. A normal package without that declaration may still install as a dependency, but DSH warns that it cannot activate it as a profile layer.

npx @deepseek-ai/dsh plugin --profile web why <package>

Only install the package source documented by the project; similarly named packages are not substitutes.

DSH Plugins is an independent community directory for discovering traceable DeepSeek Harness extensions. It organizes public project sources, install methods, compatibility, permissions, and review status. It is not an official DeepSeek AI website.

For DSH releases, platform documentation, and product support, use the official DeepSeek Harness repository.

These are directory labels for discovery. Plugin means a mountable extension; Collection groups several coordinated extensions; Skin changes an interface's visual layer; Skill provides instruction and resource content for an agent. A project's actual manifest and install method remain authoritative.

The labels describe how a project is used, not its popularity or verification status.

Community means the listing is based on traceable public metadata but has not completed directory checks. In review means checks are underway. Verified means one specific version passed the published baseline for installability, documentation, permissions, license, and behavior.

Verified is not a security guarantee and never replaces source review, permission review, or sandbox testing.

The catalog is generated from a curated source list plus public GitHub and npm metadata snapshots. Stars, downloads, versions, and repository activity can change after a snapshot, while translated descriptions and project types are maintained editorially.

Open the linked source before installation when freshness or provenance matters.

Start with source ownership, project type, install source, compatibility, permissions, and verification status; then inspect the repository and test in an isolated profile. To submit, the site generates a structured Markdown draft and opens GitHub Discussions for a public review trail.

The submission form does not send data to this site; your browser copies the draft for you to post.

The plugin command manages dependencies for one DSH profile, so it must know which profile to initialize or update. Put the DSH-owned --profile flag before the pnpm command that follows.

npx @deepseek-ai/dsh plugin --profile web search "web ui"

Use web, headless, or the name of an existing custom profile.

DSH forwards plugin operations to a pnpm executable on your PATH; npx installs DSH for the current run but does not install pnpm for its child process. The current DSH source workspace pins pnpm 11.7.0.

corepack enable
corepack install --global pnpm@11.7.0
pnpm --version

If Corepack is unavailable, install the same version with: npm install --global pnpm@11.7.0

DSH forwards search verbatim to pnpm search, which searches the full npm registry rather than this curated directory. Add ecosystem terms such as dsh-plugin, then check the package source and its dsh.bundle manifest before installing.

npx @deepseek-ai/dsh plugin --profile web search dsh-plugin "web ui"

Use this directory when you need project type, source, install method, and verification status together.

pnpm 10 and newer block dependency build scripts until they are explicitly allowed. DSH prints the resolved profile directory and exact package key. Add only that reviewed package under allowBuilds in the profile's pnpm-workspace.yaml, then rerun the add command.

allowBuilds:
  exact-package-name: true

Do not broadly allow every build script; install scripts execute code on your machine.

A profile alone is not an operation. Supply a pnpm command such as add, remove, search, or why after the profile option.

npx @deepseek-ai/dsh plugin --profile web add <package>
npx @deepseek-ai/dsh plugin --profile web remove <package>
npx @deepseek-ai/dsh plugin --profile web search <terms>

Relative file:, link:, ./, and ../ package paths are resolved from the directory where you invoke DSH.

Record all three runtime versions, the profile name, the full command, and the resolved profile directory printed by DSH. DeepSeek Harness is still a release candidate, so version-specific reports matter.

node --version
pnpm --version
npx @deepseek-ai/dsh --version

The current source workspace expects Node ^22.19.0 or >=24.0.0.