Bridges Multica to DeepSeek Harness through a versioned JSONL process protocol.
Install
# from npm (prebuilt)
dsh plugin --profile web add dsh-profile-multica
# from GitHub (first run asks for allowBuilds approval — follow the hint, retry)
dsh plugin --profile web add github:caizhihaoczh/dsh-profile-multica
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 | 中文
An installable community bundle that exposes the official DeepSeek Harness CLI to Multica through a versioned JSONL process protocol.
See the protocol reference for request, event, cancellation, and exit semantics.
The bundle adds three commands to a dedicated profile:
dsh --profile multica --probe
dsh --profile multica --list-models
dsh --profile multica --stdio
--probe prints the discovery frame used by Multica. --list-models projects the installed DSH providers, models, and reasoning levels. --stdio accepts one version-1 execute request, streams Agent and Session events as JSONL, accepts cancellation for the active request, flushes persistence, prints one terminal result, and exits. Protocol frames use stdout; diagnostics use stderr.
An execute request can create a fresh Agent or resume a persisted Session, select a provider/model/reasoning level, and mount task-scoped stdio or Streamable HTTP MCP servers. MULTICA_DSH_SESSION_ROOT selects the JSONL persistence directory. DSH_PERMISSION_MODE may be read-only, workspace-write, or danger-full-access; the default is workspace-write. This transport has no interactive approval round trip, so operations outside the selected policy fail instead of waiting.
Requirements
- Node.js
^22.19.0or>=24.0.0 @deepseek-ai/dsh0.1.0-rc.7or a compatible later prerelease- pnpm on
PATHfordsh plugin
Install
After the package is published to npm:
npm install --global @deepseek-ai/dsh@0.1.0-rc.7
dsh plugin --profile multica add dsh-profile-multica
dsh --profile multica --probe
To install a local checkout, build a tarball first:
pnpm install
pnpm pack
dsh plugin --profile multica add /absolute/path/dsh-profile-multica-0.1.0.tgz
dsh --profile multica --probe
The plugin command creates the multica profile over the official dsh-base, installs this bundle, and appends its declared patch layer. Profile installation and the Multica daemon must run as the same OS user and use the same DSH_HOME when it is customized.
Develop
pnpm install
pnpm run typecheck
pnpm test
pnpm run build
pnpm run smoke:pack
pnpm pack
smoke:pack packs the current checkout, installs the tarball into an isolated profile using the supported official DSH release, verifies --probe, and removes the temporary profile.
Before publishing, add the dsh-plugin GitHub topic and verify the packed tarball against a clean official CLI installation.
Model experience
The bridge adds no system-prompt text or tool schema. It submits Multica input as an ordinary user message and projects existing DSH events.
Limitations
- One process accepts one execute request; Multica launches a fresh process per task.
- The protocol has no approval response. Choose an appropriate non-interactive permission mode for the target environment.
- Model discovery reports a failing provider on stderr and continues with the remaining providers.
- The package tracks prerelease DSH APIs, so a new DSH prerelease may require a matching plugin release.
License
MIT
Links
More in this category
yjh051108/dsh-routing-suite★ 7000
One repository, three parts: a runtime injector for DSH plugin packages (inject, hot-reload, unload, promote a dev staging tool to the front, route self-heal, plus a settings-page plugin manager that lists, unloads and drags folders in to internalize), a task-aware reasoning-mode router agent preset (router-standard / router-spec / router-react), and a graded two-level task protocol whose six tools (commit_star, lock_stage, revise_do, edit_plan, mark_task, redteam_verdict) pin task state to disk. The injector implementation ships in-tree, so the install carries its own behaviour rather than a dependency list.
strukto-ai/mirage#dsh★ 3678
Swaps the filesystem and bash providers for a mirage virtual workspace: file tools and shell commands run over mounted resources (RAM, S3, Redis, Slack, Gmail, Notion, Postgres) instead of the host disk, with per-mount read/write/exec modes, per-command sandbox routing (monty, pyodide, quickjs in process; docker, e2b, daytona remote), and installed CLIs (git, gh, slack, linear, ntn, gws, or one you register) as head words in the virtual terminal.
hust-open-atom-club/oh-dsh★ 324
Community distribution: TUI, desktop, and Web UI as one bundle with layered installation.
weijiafu14/pi2dsh★ 212
Pi Host ABI compatibility engine: after one install, unmodified Pi extensions from npm mount as native DSH plugins with `dsh plugin add <pi-package>`. Verified end to end on stock DSH with pi-mcp-adapter (full MCP manager: OAuth, resources, prompts, MCP Apps, elicitation, sampling), @tintinweb/pi-subagents, pi-code, pi-hermes-memory and pi-background-tasks; `pi2dsh inspect` reports a package's compatibility before installing.
Fishquito7/dsh-skill-mcp-panel★ 175
Manages DSH skills and MCP servers from the web settings: skill cards with hot enable/disable, workspace scopes, groups, batch migration and drag-and-drop import, plus stdio/HTTP MCP CRUD with connection tests, secret redaction and the unified dsh-panel CLI.
lire1131/dsh-undo-savepoint★ 172
Undo/redo & rollback system for DSH: every config change is auto-snapshotted; undo/redo/restore to any version from the WebUI or the offline CLI/GUI tools (works even when DSH fails to boot).
Community comments
Comments are public GitHub Discussions. Loading them connects to GitHub and Giscus; a GitHub account is required to post.