dushaobindoudou/dsh-acp ↗★ 9

dsh-acp-server

提供ACP服务器插件以从外部客户端驱动智能体 适合需要从Zed等外部ACP客户端调用和控制DSH智能体的开发者。

包名
dsh-acp-server
兼容性
待验证
版本
0.14.2
许可证
MIT
最近更新
2026年10月14日

安装

$npx -p @deepseek-ai/dsh dsh plugin --profile web add github:dushaobindoudou/dsh-acp

Configuration

All knobs have schema defaults; override only the keys you want in your profile layer ($DSH_HOME/profiles//cordis.patch.yml). Full samples in examples/patches/.

KeyTypeDefaultDescription
agentNamestringdshinitialize.agentInfo.name shown to clients
providerstring-pin the model for ACP sessions (must be set with model)
modelstring-pin the model for ACP sessions (must be set with provider)
tokenstring-extra ACP bearer credential for web-mounted mode; otherwise DSH Web's login cookie is required. Standalone serve takes --token
offerAlwaysPermissionsbooleantrueinclude allow_always / reject_always options in permission requests
flushOnTurnEndbooleantrueflush session persistence after every completed turn
hostControlbooleantrueexpose dsh/remote/* host methods
hostControlDenystring[][]block endpoints such as settings/*, workspace/delete, or *
- id: acp-server
  config:
    agentName: my-dsh
    provider: liepin        # pin (or omit both to follow the live default)
    model: glm-5-3

Behavior follows the harness config conventions: the schema validates at plugin load (wrong types or a half-set provider/model pin fail loudly with the exact key), missing keys fall back to defaults (a patch layer replaces the whole config value, the schema refills the rest), and an unset provider/model follows the profile's agent-default-model - read per session, so in-GUI model switches apply to new ACP sessions too.

Model credentials come from the usual dsh places ($DSH_HOME settings / provider API-key envs), shared with the web UI - no second setup.