DeepSeek Harness Plugin

DamonKoy/dsh-plugin-toggle

Stars ★ 4 Category Development & Runtime Added 2026-08-15

Settings -> Plugins switchboard: every loaded plugin card shows its package description and runtime phase, with fuzzy search and start/stop toggles that never rewrite config files.

Install

# from GitHub (first run asks for allowBuilds approval — follow the hint, retry)

dsh plugin --profile web add github:DamonKoy/dsh-plugin-toggle

Any plugin you install runs third-party code with your own permissions — it can read your files, use your credentials, and reach the network, and tool approvals don’t sandbox it. GitHub-sourced plugins also run build scripts at install time — pnpm blocks those until you allow them, so an install can stop with ERR_PNPM_GIT_DEP_PREPARE_NOT_ALLOWED or ERR_PNPM_IGNORED_BUILDS; dsh prints the exact key to add under allowBuilds in your profile’s pnpm-workspace.yaml, and the install works on the next run. Allowing a build is a trust decision: only install sources you trust, and pin a commit (github:owner/repo#sha).

README

English | 中文

A DeepSeek Harness (DSH) plugin switchboard for the web GUI.

Open Settings → Plugins → Plugin Switch. Every loaded plugin is a card with:

  • a short description (from that package's package.json description)
  • enabled / disabled + fiber phase (running / pending / failed / …)
  • Start / Stop (runtime only — does not rewrite cordis.yml)
  • fuzzy search (name / module / id / description; subsequence match)

Core / surface plugins (webserver, connection, session, agent, …) are marked Core and cannot be stopped from this UI, so the page cannot take itself down.

Install

dsh plugin --profile web add github:DamonKoy/dsh-plugin-toggle

Restart dsh web, then open Settings → Plugins → Plugin Switch.

Or add the repo as a profile dependency and include the bundle:

{
  "dependencies": {
    "dsh-plugin-toggle": "github:DamonKoy/dsh-plugin-toggle"
  },
  "dsh": {
    "profile": {
      "bundles": ["dsh-plugin-toggle"]
    }
  }
}

Then pnpm install in the profile directory and restart dsh web.

What you get

Feature Notes
Plugin cards Title, entry id, description, enabled tag, phase
Categories Grouped sections (core / UI / theme / tools / fun / other), collapsible
Sorting Within a group: togglable plugins first, then by status (running first), then name
Fuzzy search Tokens match as substring or subsequence across fields incl. category
Start / Stop entry.update({ disabled }) — runtime only, no tree.write()
Core guard Surface/runtime entries cannot be stopped (id- and module-name-based); others need a two-step confirm
Usage history Every toggle is persisted to ~/.dsh/dsh-plugin-toggle.jsonl (last 1000), shown in a collapsible “使用记录” section
Persistence Installed as a composition plugin — survives dsh web restarts

HTTP API (same origin)

Method Path Role
GET /plugin-toggle/list { entries: [...] }
GET /plugin-toggle/logs { records: [...] } (recent usage history, newest first)
POST /plugin-toggle/set { entryId, enabled } → { ok, entry? | message? }

POST is same-origin only.

Layout

dsh-plugin-toggle/
  lib/index.js          Host: list + set routes over the Cordis Loader
  client/client.js      Client: Settings tab (ModuleLoader factory)
  cordis.patch.yml      Bundle insert (`id: plugin-toggle`)

The client exports.inject is the service name slots (not a package name). Using package names here parks the client fiber forever.

License

MIT

Content from the project README on GitHub ↗

Links

GitHub repository ↗ Install via dsh-market ↗

More in this category

View the whole category →

Community comments

Comments are public GitHub Discussions. Loading them connects to GitHub and Giscus; a GitHub account is required to post.