forrestchang/dsh-multica-runtime

Run the dsh runtime on Multica.

The integration layer that lets Multica drive the public DeepSeek Harness as a runtime, without either side forking the other. It builds a local bundle from a checkout, installs it into a multica profile, and speaks a versioned JSONL protocol over stdio to the Multica daemon: --probe reports the protocol version the daemon uses to discover the profile, --list-models exposes model and thinking-level discovery from DSH internals, and --stdio runs the session. It applies a bundle patch that disables DSH telemetry and keeps stdout strictly for protocol traffic.

Development & Runtime ★ 0 updated 2026-08-14
View on GitHub ↗

Install

pnpm install
pnpm check
pnpm build
dsh plugin --profile multica add /absolute/path/to/multica-dsh-runtime

README blocks quoted verbatim: the local-development block (pnpm install, pnpm check, pnpm build) followed by the README's install line, which adds the built checkout by absolute path into a multica profile. The README also documents pointing a non-standard dsh install at its launcher with export MULTICA_DSH_PATH=/absolute/path/to/dsh. Registry check 2026-09-16: dsh-multica-runtime returns 404 on npm, so no version is asserted.

Compatibility

README: a private, out-of-tree runtime bridge that exposes a versioned JSONL protocol over stdio and composes over @deepseek-ai/dsh-base — it does not require changes to DeepSeek Harness and does not vendor or redistribute harness source. DSH telemetry is disabled by the bundle patch, stdout is protocol-only with diagnostics on stderr, and Multica discovers the profile only after dsh --profile multica --probe returns protocol version 1. The README also documents --list-models and --stdio. Repo verified 2026-09-16 (65★, last push 2026-08-14).

Details

Recent updates

The README documents the runtime contract, the privacy posture and the commands rather than a release-by-release table.

FAQ

How do I install it?
Build the checkout (pnpm install, pnpm check, pnpm build) and then run dsh plugin --profile multica add /absolute/path/to/multica-dsh-runtime, per the README.
Which harness version is it validated against?
The README states the checkout is currently validated against @deepseek-ai/dsh@0.1.0-rc.6 and its matching @deepseek-ai/dsh-* package family.
How does Multica find the profile?
Per the README, Multica discovers it only after dsh --profile multica --probe returns protocol version 1.

More plugins in Development & Runtime

Browse more in Development & Runtime

Guides for Development & Runtime plugins