dsh-acp-plus
为DSH提供扩展的智能体客户端协议服务端包 适合需要将Zed等外部编辑器或客户端连接到DSH进程的开发者。
安裝
npx -p @deepseek-ai/dsh dsh plugin --profile web add github:AndPuQing/dsh-acp-plus說明文件
閱讀完整 README ↗Usage
dsh --profile acp-plus
stdout carries only ACP JSON-RPC; diagnostics go to stderr. Connect any ACP client to the process.
Zed
Zed starts external agents through agent_servers. In a remote project the
agent runs on the remote Zed server, so the setting belongs in the remote
server settings (zed: open server settings, i.e. the remote
~/.config/zed/settings.json):
{
"agent_servers": {
"dsh-acp-plus": {
"type": "custom",
"command": "/bin/sh",
"args": ["-lc", "exec dsh --profile acp-plus"],
"env": {}
}
}
}
sh -lc picks up the login shell's PATH; an absolute dsh path works too.
Reconnect the remote project and select dsh-acp-plus in the agent picker.
Modes, slash commands, session/load replay, and ask_user_question (when the
client declares form elicitation) are available; client terminals are
intentionally unsupported. Logs:
~/.local/share/zed/logs/server-preview-*.log.
Configuration
The profile patch configures the bridge row:
| Field | Type | Default | Description |
|---|---|---|---|
provider | string | agent-default-model | Provider route for new agents (e.g. deepseek-official). |
model | string | agent-default-model | Exact model id (e.g. deepseek-v4-flash). |
sessionListPageSize | integer >= 1 | 100 | Maximum sessions returned by one session/list page. |
enableSessionLoad | boolean | false | Advertise and serve session/load transcript replay. |
enableAdditionalDirectories | boolean | false | Accept additionalDirectories with containment-checked pre-approval. |
The shipped profile enables both enableSessionLoad and
enableAdditionalDirectories.
Inspect the composed configuration and its schema:
dsh --profile acp-plus --dump-config
dsh --profile acp-plus --dump-config-schema
Models and credentials
provider / model are optional. When unset, the bridge follows
agent-default-model — the default model service the dsh Web Models page
writes — so a deployment configures its model once and every entry point
follows. Provider routes (llm-pi-ai providers) and the default model can be
shared across profiles by putting them in $DSH_HOME/cordis.patch.yml.
Note that a DSH patch replaces the whole config object of the row it targets:
overriding the acp-plus row requires restating sessionListPageSize,
enableSessionLoad, and enableAdditionalDirectories. Configuring only the
model does not touch that row.
API keys are home-level and shared by every profile
($DSH_HOME/.credentials.yaml, written by the Web Models page or supplied
through the launch environment).