DSH HUB
HomePlugin StorePlugin PacksCommunityRankingsResourcesPublish Guide
Plugin source
Back to catalog

d0nj /

d0nj/dsh-plugins

Topic repository only

My DeepSeek Harness plugin collection

★ 1 Stars0 Forks0 IssuesN/A Community rating0 Confirmed installs
View on GitHub
READMESource: main@64bfd0f9

d0nj plugins for DeepSeek Harness

A collection of Cordis bundles for DeepSeek Harness, managed as a Turborepo monorepo.

Each package is a dsh bundle: it declares dsh.bundle.patch in its package.json, and installing it adds plugin rows to a profile. The Harness loads built JavaScript from dist/, so the TypeScript here is compiled before installation.

Packages

Package What it adds
@d0nj/dsh-websearch-multi Thirteen web_search backends and four web_fetch backends behind the existing ctx.web seam.
@d0nj/dsh-ui-custom Theme presets, colour tokens, typography and geometry for the Web UI, with a live editor.
@d0nj/dsh-git-bash A working bash tool on Windows, backed by Git Bash, beside the shipped pwsh tool.
@d0nj/dsh-agent-rules AGENTS.md as binding system-prompt sections, replacing the advisory reminder that agents can talk themselves out of.
@d0nj/dsh-browser A real Chrome window for the agent: the browser tool opens pages, reads them as numbered accessibility outlines, and clicks, types and scrolls by ref.

Requirements

  • Node.js 22 or newer
  • pnpm 12
  • A dsh installation on PATH

Working in the repo

pnpm install          # install workspace dependencies and real Harness type packages
pnpm build            # compile every package to dist/
pnpm typecheck        # strict TypeScript check, tests included
pnpm test             # node --test over the compiled tests
pnpm check            # syntax-check the emitted entry points
pnpm clean            # remove dist/ and dist-test/

pnpm build is what produces the files a profile loads. Turbo caches it, so a change to one package rebuilds only that package and its dependents.

Adding a plugin

  1. packages/<name>/ with a package.json declaring dsh.bundle.patch, plus cordis.patch.yml, locale/en.json, and icon.svg.
  2. src/index.ts exporting apply, and optionally Config / inject.
  3. tsconfig.build.json extending ../../tsconfig.base.json.
  4. pnpm install, pnpm build, then install it into a profile.

Installing a plugin into a profile

The Harness installs a bundle by absolute path, so pass the directory this repository was cloned into:

plugin_manager({ action: "install_bundle", target: "<absolute path to this repo>/packages/websearch-multi" })

A linked directory install picks up rebuilt files, but the Host runs in-process, so a module change needs a restart before the new code loads.

Releasing

Bump the package's version in package.json and merge to main. The publish workflow then verifies the workspace, uploads every manifest version the npm registry does not have yet, and creates the matching <package>@<version> tag. Pushing that tag by hand still works, and a push carrying no new version publishes nothing.

Publishing uses npm OIDC trusted publishing, so no registry token is stored here. The first version of a new package still has to be published once by hand, because trusted publishing cannot create a package.

Dependency updates

.github/renovate.json5 groups the Harness packages into a single "DeepSeek Harness" pull request and rewrites peerDependencies together with devDependencies. That pairing matters: the Host refuses to load a bundle whose declared dsh-* peers do not satisfy its own version, and Dependabot does not update peerDependencies at all.

The config only runs once the Renovate app is installed on this repository. Bump the package version in the pull request it opens; merging publishes the release.

—/ 5

No ratings yet

Manifest verification required

Commit 64bfd0f942a5

Community comments

No comments yet. Be the first to write one.

DSH HUB

A community index for DSH plugins. Not an official GitHub or DeepSeek AI product.

CommunityResourcesAPIAbout