dsh-software-tools

Sidebar 🔧 软件工具 manager for DeepSeek Harness Web. Maintain a curated inventory of local software — WSL CLI tools and Windows apps reachable via interop — and check the ones you want the model to know about. The checked set is injected into the model's system prompt as a compact section, so every session knows what software exists on this machine and how to call it. 中文说明见 README.zh.md。

Problem

A model (e.g. deepseek-v4-flash) has no idea that you have IDM, ComfyUI, Obsidian, aria2… installed, let alone how to invoke each one. This plugin turns "local software inventory + invocation recipes" into a checkable, persisted, auto-injected system-prompt section: the model reads the usage field and runs the ready-made command.

Features

Install

dsh plugin --profile web add dsh-software-tools

If your pnpm supply-chain policy blocks dsh plugin add, install manually: copy the package into ~/.dsh/profiles/web/node_modules/ and append to ~/.dsh/profiles/web/cordis.patch.yml:

- insert:
    - id: dsh-software-tools
      name: dsh-software-tools
      config: {}
- insert:
    - id: software-tools-skill
      name: '@deepseek-ai/dsh-skill-filesystem'
      config:
        providerName: software-tools-skill
        includeDefaultRoots: false
        customSkillDirs:
          - !!js process.getBuiltinModule('node:path').join(process.getBuiltinModule('node:path').dirname(process.getBuiltinModule('node:module').createRequire(baseUrl).resolve('dsh-software-tools/package.json')), 'skills')

Restart dsh web and hard-refresh (Ctrl+Shift+R). A 软件工具 row appears in the panel rail (between Automation tasks and Task Board).

Configuration

All optional; zero-config by default:

State files

Entry fields: id ([a-z0-9-]{1,32}, unique), name, category (download/proxy/media/browser/knowledge/runtime/model/misc), desc (≤40 chars, panel only), usage (≤5 directly executable lines, injected into the system prompt).

An entry is usage instructions only: written for the session that is about to call the tool — what it is, when to use it, the first command to run. Tuning/ops/troubleshooting/history (VRAM gates, quantisation and KV flags, measured throughput, port-change steps, migration history…) does not belong here; it belongs in the tool's own docs (README / deploy report / cheat sheet), with at most a details in <path> pointer. The entry is injected on every request, so length is cost — and tuning needs far more context than a few lines.

Adding a tool

Tell the model "add XXX to 软件工具" — the bundled add-software-tool skill researches the software and writes it into catalog.json (no rebuild, no restart; visible on panel refresh). You can also edit catalog.json by hand.

How it works

• Host half (src/index.ts): registers systemPrompt.section (software-tools, order 200) rendered from the current selection, plus the loopback RPC channel / _dsh-software-tools (list / set).
• Browser half (src/client/): contributes two official seats — sidebar.panellist (list: the rail row, whose id is the panel key and whose label is a thunk so the title follows the active locale) and main (keyed: the panel body the layout renders in the centre). Both wait on ctx.slots.inject(key, ...) for ui-layout / ui-sidebar to declare the seat. Built by tsdown into a lazy-CJS __ModuleLoader__ bundle (React comes from the host shell).
• Skill (skills/add-software-tool/): mounted via dsh-skill-filesystem's customSkillDirs, scoped to the plugin's own directory so user skill roots stay untouched.

License

MIT