Every package here is an installable dsh bundle: pure ESM, no build step, so it runs from npm, from git, or straight from a checkout while you edit it.

Anywhere dsh runs, these run: the CLI, dsh Desktop on macOS and Windows — whose plugin manager installs any of them by name, URL or local path — or dsh Android on a phone.

Plugins

Three kinds, told apart by dsh.category in each package — what a plugin extends decides where it can be seen from:

The second half of the category is the domain: tools/finance and ui/finance cover A-share market data, information feeds and portfolio state; tools/vision reaches a multimodal model on behalf of a text-only one; tools/ecommerce covers cross-marketplace product research; tools/documents works on the files themselves; tools/game makes 2D game art; runtime/provider, runtime/observability, runtime/reliability and runtime/llm cover shared credentials, measurement, retries and gateway compatibility; runtime/im drives sessions from a chat app; ui/productivity covers the web client's own ergonomics; ui/observability makes what the agent is doing visible to the person watching.

Pick what you need

tools/ — capabilities the model can call

runtime/ — behaviour around the harness, invisible to the model

ui/ — web client extensions

Each plugin's own README, in English and 中文, is the accurate account of what it does and what it costs to run. Install any of them by package name:

dsh plugin --profile web add dsh-plugin-astock

Looking for something this repo does not ship? CATALOG.md lists plugins maintained elsewhere, by category.

[!NOTE] Finance plugins share one credential through the tushare provider rather than each asking for the same token. Every tool that needs it says so in its own description, so the model can choose a free tool when one will do — and tell you exactly what is missing when one will not.

Install

Into a dsh profile, from npm:

dsh plugin --profile web add dsh-plugin-astock

Or from a checkout — also how you develop against a running profile, since the install is a symlink and edits take effect on the next service restart:

dsh plugin --profile web add ./packages/astock

Verify it landed in the composed tree before starting anything:

dsh --profile web --dump-config      # look for the plugin's row

Configure

A plugin that exposes a Schemastery Config is configurable without touching a command line: a desktop shell — dsh Desktop, for one — renders the form at install time. The values end up as an id-targeted override in the profile's cordis.patch.yml, which you can also write by hand:

- id: astock
  config:
    tushareToken: 'your-token'

[!IMPORTANT] Later layers win per row, and a patch replaces a row's whole config rather than merging keys — so restate every key you need when overriding someone else's row.

Tool presentation — whether a session dispatches tools natively, through Code Mode, or both — is chosen once per agent preset and applies to every tool in the session, not per plugin. Some plugins here require a particular mode, and the choice affects every other plugin you install: tool presentation modes.

Develop

npm install                                        # root; resolves peer deps for every package
npm test                                           # every package
npm test -w dsh-plugin-astock                      # one package
node --test packages/astock/test/*.test.js   # one file

Tests use Node's built-in runner (node:test) — no test dependencies, no build, matching the way the plugins themselves load. They exercise the real published entry (lib/index.js) and the real defineTool, so a schema violation fails in unit tests instead of at dsh startup.

[!TIP] Green tests are not the whole bar — they never touch the Loader or a real composition.

CLAUDE.md carries the full working spec — plugin lifecycle, config, tool authoring, waterfall extension points, bundle layering, the test convention, and the verification checklist to run after changing a plugin. It is addressed to AI coding agents, but the rules are the same ones a human contributor needs.

Contributing

1. Read the guide for what you are building: tools (capabilities the model calls), runtime (waterfall wrappers and shared services) or ui (web client extensions).
2. Create packages/<name>/ with package.json (including dsh.category), cordis.patch.yml, lib/index.js, README.md and LICENSE.
3. Export name / inject / apply as named exports. A default export makes the loader drop inject, and the plugin then fails in a way that looks like something else entirely.
4. Add test/plugin.test.js covering the export shape and every registration.
5. Run npm test and the checklist in CLAUDE.md.

Four names travel together and are easy to confuse:

Related projects

dsh-desktop and dsh-android come from the same author as this repository. Both are unofficial and unaffiliated with DeepSeek.

License

MIT — see LICENSE.