openma-ai/deepseek-harness-acp
ACP server implementation for DeepSeek harness
deepseek-harness-acp lets you use DeepSeek Harness from Agent Client Protocol (ACP) clients such as Zed and Backchat. 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 saved in the dsh Web UI, or dsh-acp login saves one to the same store. Both install shapes share $DSH_HOME, so conversations started in the Web UI can be listed and loaded from the editor. It is not only a CLI wrapper — it is the ACP surface plugin used by other dsh applications, letting one Host composition expose the same sessions, tools, presets, skills, and persistence through a transport chosen by the surface.
Install
dsh plugin --profile acp add @openma/deepseek-harness-acp@latestTwo install shapes. A (recommended, dsh profile plugin): npm install -g @deepseek-ai/dsh, save your API key once with dsh web, then dsh plugin --profile acp add @openma/deepseek-harness-acp@latest and run Zed with dsh --profile acp. B (standalone server): npm i -g @openma/deepseek-harness-acp, then run dsh-acp. Both shapes share $DSH_HOME — the same credential store, settings, presets, and session logs as dsh web. Published on npm (0.4.24).
Compatibility
Node >= 22.15. ACP protocol v1 clients such as Zed and Backchat. Composes the harness in-process and reuses the key saved in the dsh Web UI, or dsh-acp login saves one to the same store. Other dsh surfaces (e.g. the TUI profile) can mount the transport-independent @openma/deepseek-harness-acp/plugin on their Base Host tree.
Details
- Repo: openma-ai/deepseek-harness-acp
- Category: Other
- Stars: 12
- Version: npm @openma/deepseek-harness-acp 0.4.24; Apache-2.0; Node >= 22.15; ACP protocol v1
- Last push: 2026-09-20
- First seen: 2026-08-13
Recent updates
The current README documents the two install shapes (profile plugin vs standalone server), the in-process composition, the full ACP vocabulary mapping, credential handling, and the TUI profile path that starts a separate TUI Client process over stdin/stdout.
FAQ
- Do I need an API key in my editor config?
- No — credentials never touch your editor config; it reuses the key saved in the dsh Web UI, or dsh-acp login saves one to the same store.
- Can I load Web UI conversations in Zed?
- Yes — both shapes share $DSH_HOME, so conversations started in dsh web can be listed and loaded from the editor.
- Which clients work?
- Any ACP protocol v1 client, such as Zed and Backchat (README names both).
Alternatives
cofy-x/axern · shaokeyibb/dsh-plugin-product-subagents · openma-ai/deepseek-harness-tui