dsh-hub-cli

DSH Hub CLI

English · 简体中文

Share your DeepSeek Harness plugins and configuration as a versioned Profile.

Capture the plugins, order, runtime, and config you have running locally. Publish it as an immutable Release. Anyone can apply it with a single command, review every change before it lands, and roll back if they don't like it. 🌐 dshpluginhub.ai · Browse Plugins · Explore Presets · Docs

This repository is the open-source client for the Hub. The website, API, and registry live at dshpluginhub.ai .

Quick start · Why Presets · Commands · Support · Contributing · Governance · Security That one command installs the exact plugin versions, in the exact order, with the exact patch the author published. Not "whatever is latest today." What they had. Why shareable Presets

A DeepSeek Harness (DSH) setup is more than a list of plugins. It is a specific runtime version, a set of plugins at specific versions, the order they load in, a cordis.patch.yml that wires them together, and a handful of environment variables that hold your keys.

Getting that onto a colleague's machine usually means a wiki page, a Slack thread, and an afternoon of "works on my machine."

DSH Hub turns that setup into a first-class, versioned artifact. Browse community Presets, or build one in the web builder, at dshpluginhub.ai/profiles . What's inside a Preset Release

A Release is a small, content-addressed document. The CLI verifies its hash before doing anything with it. Runtime pins the exact DSH version the author verified against. Bundles are ordered. npm sources carry integrity hashes. GitHub sources must point at a full 40-character commit, never a branch. Patch is the author's cordis.patch.yml, published verbatim. Inputs declare which environment variables the Preset needs. The CLI refuses to publish a patch that contains a credential-looking value. Quick start

Requires Node.js 22.13+ and pnpm on your PATH.

Apply someone's Preset