Back to directory

dsh-hub-cli

Curated pickMaintenance: Active

pax-beehive/dsh-hub-cli

Open-source CLI, schemas, resolver, and DSH agent tools for DSH Plugin Hub

View on GitHubHomepage
$ npm install --global @dsh-plugin-hub/cli

102

stars

2

forks

TypeScript

Language

MIT

License

2026-08-25

Created

2026-09-02

Last push

MIT-licensed, TypeScript CLI + DSH agent-tool adapter that turns a DeepSeek Harness setup into a versioned, content-addressed Profile you can share, apply atomically, and roll back — with plan approval gates, pinned sources, and secrets that stay local.

DSH integration

Native runtime

Author-claimed

Safety audit

Unaudited

Last verified

2026-09-04

License

MIT

01What can it help you accomplish?

  • Package your whole local DeepSeek Harness setup as one versioned, reproducible Profile and publish it

    An immutable, content-addressed Release that locks the exact plugin versions, load order, runtime, and cordis.patch.yml so anyone can apply it with a single command

    Developers and platform engineers who want to reproduce a DSH environment across teammates, CI runners, and AI agents from a single reviewable snapshot

  • Apply a teammate's Profile to your local harness and upgrade or roll back safely

    A staged, validated, atomic swap of the local Profile; the previous Profile directory and lockfile are kept intact as a full revision, so rollback is a rename rather than a reinstall

    Teams that must deploy DSH config consistently across machines and CI and require every change to be reviewable and reversible

02How to install into DeepSeek Harness

Prerequisites

  • Requires **Node.js 22.13+** and **pnpm** on your `PATH`.

Installation steps

  1. 01

    $ npm install --global @dsh-plugin-hub/cli

  2. 02

    dsh-hub --help

Verify the integration

  • dsh-hub --help
  • dsh-hub profile doctor --profile web

03DSH integration and capability boundaries

DSH integrationNative runtime

Installs into DeepSeek Harness as a DSH agent-tool adapter via the official `dsh plugin add` command, exposing the dsh-hub plan/apply/rollback pipeline to the DSH agent; the other packages (schemas/registry/cli) run as a local CLI.

  • Profile share / publish

    Local Profile directory (e.g. ~/.dsh/profiles/web)An immutable, content-addressed Release (sha256-verified)

    `dsh-hub login` writes a Hub login session to ~/.dsh/.hub/auth.jsonprofile share reads the local DSH Profile and cordis.patch.yml and publishes them to the Hub
  • Profile apply (staged / validated / atomic)

    Published Profile slug + versionAn atomically swapped local web/ Profile; the prior directory is retained as a revision

    Edits the local DSH Profile directory and lockfileapply first writes a plan and only runs after the exact plan ID is confirmed
  • DSH agent-tool adapter (dsh-plugin)

    Install @dsh-plugin-hub/dsh-plugin into a ProfileEleven DSH agent tools that map one-to-one onto the CLI (search / plan / apply / diff / doctor / share / rollback)

    Mutating tools only ever create plans; execution needs confirmed: true set by the user after approving the exact plan
  • Content-addressed integrity & plan safety

    Release and local harness statesha256 comparison, plan precheck, and staging validation before any swap

04Who is it for? When not to use it?

Good for

  • Developers and platform engineers who want to reproduce a DSH environment across teammates, CI runners, and AI agents from a single reviewable snapshot
  • Teams that must deploy DSH config consistently across machines and CI and require every change to be reviewable and reversible

Not for

  • GitHub sources must point at a full 40-character commit and npm sources carry integrity hashes; every Release is content-addressed and the CLI verifies its sha256 before doing anything with it, refusing mismatches.
  • Every mutation first writes an exact, expiring plan; it is rejected after 30 minutes or if local state changed. A DSH agent can only run a plan via dsh_hub_operation_apply with confirmed: true, which it may set only after the user approves that exact plan.
  • `profile share` refuses patches containing credential-looking values and publishes only environment-variable references; secrets never leave the local machine and tokens are stored at mode 0600.

05Compatibility, maintenance and safety notes

  • GitHub sources must point at a full 40-character commit and npm sources carry integrity hashes; every Release is content-addressed and the CLI verifies its sha256 before doing anything with it, refusing mismatches.
  • Every mutation first writes an exact, expiring plan; it is rejected after 30 minutes or if local state changed. A DSH agent can only run a plan via dsh_hub_operation_apply with confirmed: true, which it may set only after the user approves that exact plan.
  • `profile share` refuses patches containing credential-looking values and publishes only environment-variable references; secrets never leave the local machine and tokens are stored at mode 0600.
  • After a first-run notice, lifecycle commands send anonymous, aggregate-only usage events (never account, machine ID, path, config, or environment values); disable with `dsh-hub telemetry off`, --no-telemetry, DSH_HUB_TELEMETRY=0, or DO_NOT_TRACK=1.
  • DSH Hub is an independent community project and is not affiliated with or endorsed by DeepSeek.
2026-08-252026-09-02v0.2.0

MIT · actively maintained (latest release v0.2.0, 2026-09-01; created 2026-08-25)

06Frequently asked questions

What does DSH Hub CLI do?

It captures your running plugins, load order, runtime, and config into one versioned, reproducible Profile you publish as an immutable Release; anyone can apply it with a single command and roll back if needed.

How do I install it?

Run `npm install --global @dsh-plugin-hub/cli`, then `dsh-hub --help`. It requires Node.js 22.13+ and pnpm on your PATH; `dsh-hub profile doctor --profile web` confirms a healthy local Profile.

Is it safe to let an AI agent drive it?

Yes. Read-only tools run freely, but mutating tools only create plans. A single `dsh_hub_operation_apply` tool executes a plan and requires `confirmed: true`, which the agent may set only after you approve that exact plan.

Does it send my secrets anywhere?

No. `profile share` refuses patches containing credential-looking values and publishes only environment-variable references; tokens stay in `~/.dsh/.hub/auth.json` with mode 0600.

08Data and sources

  • Author-claimedgithub.com7147202dfcd3…

    Install the adapter into a Profile and your DSH agent gets eleven tools that map one-to-one onto the CLI:

  • Author-claimedgithub.com7147202dfcd3…

    Share your entire DeepSeek Harness setup as one versioned, reproducible Profile.

This page is generated from the project’s public documentation, repository metadata and a structured parse of DSH Plugins; last verified on 2026-09-04. Found an error? Submit a correction.

🏆

Best DeepSeek Harness Plugins

Twelve plugins worth installing first — picked from the whole catalog, across every category.

DSH Plugins is an independent community directory of DeepSeek Harness plugins. Not affiliated with or endorsed by DeepSeek. Third-party plugins are not security-audited — review the source before installing.

New DeepSeek Harness plugins, weekly. No spam.