DSH Plugin MarketA community catalog for DeepSeek Harness plugins

dsh-plugins

Verified Skills & agents ★ 97 0.1.1

DeepSeek Harness plugin collection: installs and registers the plugins listed in cordis.patch.yml (currently Sessions Insight). Also the workspace root they are built from.

What it is

DeepSeek Harness plugin collection: installs and registers the plugins listed in cordis.patch.yml (currently Sessions Insight). Also the workspace root they are built from.

How to install

Run this in the DSH web profile, then refresh the page.

$ dsh plugin --profile web add @cyrusdoyle/dsh-plugins@0.1.1

DSH versions accepted

Undeclared

Author and traction

Mt-Youya · ★ 97 · Updated 2026-11-06

About this plugin

English | 简体中文 Cyrus Plugins · @cyrusdoyle/dsh-plugins

A plugin collection for DeepSeek Harness (DSH). Install this one bundle to get every plugin listed below; each plugin can also be installed on its own.

Plugins Install

Requires DSH 0.2.1-rc.5 or newer (see docs/adr/0002-asar-021-is-the-contract.md). First decide which profile to install into: the desktop app uses desktop, dsh web on the command line uses web. Installing into the wrong profile does not error; the plugin just never shows up.

Install the collection (recommended) to get every plugin at once; when a plugin is added to the collection later, upgrading the collection brings it in.

Install a single plugin:

Then fully quit and reopen DSH. "Cyrus Plugins" or "Sessions Insight" in the plugin manager means it worked. Pick one of the two. The collection and the standalone plugin insert the same id into the loader tree; with both in dsh.profile.bundles, DSH fails at boot with duplicate loader entry id. Run dsh plugin --profile remove on one before switching to the other. Git installs work for the standalone plugin, not for the collection. plugins/sessions-insight/lib/ is committed, so the member can be installed straight from this repository without running build scripts — for example dsh plugin --profile desktop add github:Mt-Youya/dsh-plugins#path:/plugins/sessions-insight, or point the plugin manager at a local checkout of that directory. The collection cannot be installed from Git: its root dependencies use workspace:^, which is only rewritten to a version number by pnpm pack / publish. Install the collection from npm, or link this checkout as described below.

Installing from this working tree (developing the collection): the desktop plugin manager's "Add plugin" also accepts a local directory — point it at this checkout's absolute path. DSH records it as "@cyrusdoyle/dsh-plugins": "link: ": a symlink into your working tree, not a copy, and nothing is built for you. The host resolves lib/index.js through that link, and lib/ is gitignored, so build it first (the collection embeds the compiled stylesheet, so the CSS step comes first):

Then fully quit and reopen DSH. Later edits only need a rebuild and a restart — there is no need to reinstall.

Each plugin's usage, permission boundary and known limitations live in its own README. Settings, balance and update checks

The collection embeds the same plugin source as the standalone member (ADR 0009), so its runtime behaviour is the Sessions Insight behaviour: read-only insight, the handoff, confirmed session deletion, plus a settings page and two opt-in utilities. Settings are saved by the Host. /api/dsh-sessions-insight/settings is read-only; the six switches (session overview, Skills tab, cumulative level chart, expand tools by default, balance display, automatic version checks) are written through the Host's configuration form and stored by the Host. The plugin writes no config file. Balance and version checks are off by default. Turning one on — or pressing its button — is the only thing that makes the plugin call out. Outbound traffic is limited to two fixed HTTPS endpoints, https://api.deepseek.com/user/balance and https://registry.npmjs.org/@cyrusdoyle%2F.../latest, with no redirects, no cookies and no caller-controlled URL. Credentials: the balance check resolves the credential reference configured for the DeepSeek official adapter (apiKeyEnv, default DEEPSEEK_API_KEY), then falls back to the signed-in DeepSeek account. Custom provider references are not followed; the plugin never stor

Similar plugins