caizhihaoczh/dsh-profile-multica

Multica JSONL bridge profile for DeepSeek Harness

An installable community bundle that exposes the official DeepSeek Harness CLI to Multica through a versioned JSONL process protocol. It adds three commands to a dedicated profile: --probe prints the discovery frame used by Multica, --list-models projects the installed providers, models and reasoning levels, and --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. A request can create a fresh agent or resume a persisted session, pick a provider/model/reasoning level, and mount task-scoped stdio or Streamable HTTP MCP servers; MULTICA_DSH_SESSION_ROOT selects the JSONL persistence directory.

Files & Data ★ 0 updated 2026-08-18 ⏳ pending
View on GitHub ↗

Install

dsh plugin --profile multica add dsh-profile-multica

README Install section quoted verbatim; the README's preceding step installs the harness itself with npm install --global @deepseek-ai/dsh@0.1.0-rc.7. Registry-verified live 2026-09-15: dsh-profile-multica latest 0.1.0 (published 2026-08-18), repository field github.com/caizhihaoczh/dsh-profile-multica.

Compatibility

README requires @deepseek-ai/dsh 0.1.0-rc.7 or a compatible later prerelease. DSH_PERMISSION_MODE may be read-only, workspace-write (default) or danger-full-access; because the transport has no interactive approval round trip, operations outside the selected policy fail rather than wait.

Details

Recent updates

The README documents the protocol rather than a release table; the latest version on the registry when checked on 2026-09-15 was 0.1.0.

FAQ

How do I install it?
The README installs the harness with npm install --global @deepseek-ai/dsh@0.1.0-rc.7, then the bundle with dsh plugin --profile multica add dsh-profile-multica.
What commands does it add?
Three on a dedicated multica profile: --probe (discovery frame), --list-models (installed providers/models/reasoning levels) and --stdio (one JSONL execute request, streamed events, cancellation, terminal exit).
How are permissions handled?
DSH_PERMISSION_MODE is read-only, workspace-write (default) or danger-full-access; the README notes the transport has no interactive approval round trip, so out-of-policy operations fail instead of waiting.

Alternatives

Aidenwu0209/dsh-Unlimited-OCR-Skill · bill9109/dsh-101 · bwndlct/dsh-session-export

More plugins in Files & Data

Browse more in Files & Data

Guides for Files & Data plugins