dushaobindoudou/dsh-acp

Agent Client Protocol (ACP) server plugin for the DeepSeek Harness (dsh) - drive dsh agents from Zed and any ACP v1 client

An Agent Client Protocol (ACP v1) server for DSH: boots the entire harness (agent loop, tools, sandbox, session persistence) and speaks JSON-RPC over stdio/HTTP so an ACP client such as Zed can drive a full dsh coding agent with streaming output, tool calls and permission prompts. Implemented methods include initialize (capability advertisement), session/new, session/prompt (streaming agent_message_chunk / agent_thought_chunk, plan updates, full tool-call lifecycle and stop reasons), session/list, session/resume, session/load (with transcript replay), session/set_mode (default ⇄ plan), available_commands_update, session/request_permission (allow/deny once or always), session/cancel and session/close.

uncategorized ★ 0 updated 2026-08-17
View on GitHub ↗

Install

dsh plugin --profile acp add dsh-acp-server

README install, prebuilt from npm (recommended — no build authorization needed); the npm package dsh-acp-server 0.11.1 (registry-verified 2026-09-11; registry repository field -> github.com/dushaobindoudou/dsh-acp) is the shipped artifact. A tarball form (dsh plugin --profile acp add ./dsh-acp-server-0.7.0.tgz) and a source form (dsh plugin --profile acp add github:dushaobindoudou/dsh-acp) are also documented — GitHub installs pull source, not build output, so pnpm >= 10 needs the package allowlisted under allowBuilds in the profile's pnpm-workspace.yaml before the prepare build runs. Verify any time with dsh --profile acp --dump-config.

Compatibility

Requires Node.js >= 22 and the dsh CLI (npm i -g @deepseek-ai/dsh). Two final forms: standalone (dsh-acp-server / npx, boots dsh --profile acp on the current stdio) or web-mounted (node bin/setup-webacp.mjs installs into the web profile so every plain dsh web serves GUI + ACP on one port; --clone webacp gives the same on a separate profile). Remote access via dsh --profile acp serve --port 7800 binds 127.0.0.1 by default; --host 0.0.0.0 --token <secret> exposes it and requires a token.

Details

Recent updates

README lists the vendor dsh/* host-plane extensions alongside the standard ACP methods, and documents the end-to-end test story: pnpm run test:e2e boots the real dsh in a throwaway $DSH_HOME with a deterministic mock LLM and asserts wire behavior over stdio, serve (HTTP+SSE), web-mounted and bare-install grace paths.

FAQ

How do I install the dsh ACP server?
Run: dsh plugin --profile acp add dsh-acp-server (prebuilt from npm, recommended). Tarball and GitHub source forms are documented; GitHub installs need the package allowlisted under allowBuilds for pnpm >= 10 to run the build.
Can I use it with Zed?
Yes — it is an ACP v1 server, so Zed or any ACP v1 client can drive dsh exactly like opencode or Gemini CLI, including streaming output, tool-call lifecycle and permission prompts.
How do I expose the ACP server remotely?
Run dsh --profile acp serve --port 7800 (binds 127.0.0.1 by default) or add --host 0.0.0.0 --token <secret> to bind publicly with token authentication.

More plugins in uncategorized

Browse more in uncategorized

Guides for uncategorized plugins