deepseek-harness-acp

deepseek-harness-acp

Use DeepSeek Harness from Agent Client Protocol clients such as Zed and Backchat .

= 22.15" /> The adapter composes the harness in-process and maps its session-event log onto the full ACP vocabulary: streamed text and reasoning, tool calls with diffs and display terminals, plans, permission requests, session modes, config options, slash commands, skills, and MCP servers. Credentials never touch your editor config — it reuses the key you saved in the dsh Web UI, or dsh-acp login saves one to the same store. One package, standalone or plugin Both shapes share $DSH_HOME: the same credential store, settings, presets, and session logs as dsh web — conversations started in the Web UI can be listed and loaded from the editor.

Other dsh surfaces can mount the transport-independent @openma/deepseek-harness-acp/plugin on their Base Host tree and own the transport adapter. The TUI profile uses this path: it starts a separate TUI Client process and connects ACP over that process's standard stdin/stdout; it does not start dsh-acp or use an in-process Client stream.

The package is therefore not only a CLI wrapper. It is also the ACP surface plugin used by other dsh applications: one Host composition can expose the same sessions, tools, presets, skills, and persistence through a transport chosen by the surface. DSH compatibility

This release supports @deepseek-ai/dsh >=0.1.7-rc.2 — a minimum-version floor declared in engines.dsh (the field dsh's own plugin loader checks, with prereleases included), never an exact-version list. It is deliberately not a @deepseek-ai/dsh peer dependency: npm and pnpm match peer ranges without prereleases, so a peer floor would reject every dsh prerelease. A newer dsh is always attempted: API differences between dsh generations are feature-detected where they are used (for example dsh 0.2.1's subagents.drainDescendants versus 0.2.0's drainContinuableDescendants), and a dsh newer than the newest tested version (0.2.1-rc.2) only logs a warning. Only a dsh below the floor is refused. CI exercises the tested profile matrix (runtime/compatibility.json) plus the next dist-tag. The bundled runtime is DSH 0.2.0-rc.2, including the upstream cross-process session write lock.

Runtime selection has exactly two rules (Martty issue #157): Standalone (dsh-acp bin): the packaged runtime is always used — ambient installs in the invoking directory, on PATH, or in global npm are never consulted. An explicit --dsh-path/DSH_PATH/DSH_ACP_HOST (or the literal value bundled) selects an installation instead, and is refused with a message naming the version found, its source, and the supported range when it falls outside it. Plugin mode (dsh plugin add, Martty launched as a dsh plugin): the hosting dsh is the runtime, checked against the same range at mount time; an out-of-range host fails with the same refusal message.

The resolved runtime is always reported: the launcher logs harness host: @deepseek-ai/dsh via to stderr, and the initialize response carries agentCapabilities._meta.dsh.runtime ({base, version, source}) for clients to display.

A competing load/resume returns a standard JSON-RPC error. Closing the session or exiting the owner process allows another process to resume it. Every process writing shared sessions must use a fixed backend; older hosts do not participate in this lock.

Restoring historical sessions uses the host's V3 migration, which preserves the original log. Upgraded sessions cannot be read by older hosts. Multi-root workspaces are supported via the bundled multi-root plugin (see Sessions under Features). A · dsh profile plugin (recommended)

The plugin command creates $DSH_HOME/profiles/acp, installs or upgrades the adapter, and registers its dsh.bundle patch. The bridge mounts over @deepseek-ai/dsh-base — the same product baseline as dsh web, with the module-reload watcher off. Extend th