_Kerman
31a49c6629
# Conflicts: # docs/capability-seams.i18n.yaml # docs/tool-catalog.i18n.yaml # packages/bundle/base/package.json # packages/core/agent-loop/tests/serial-listener-review.spec.ts # packages/core/agent-tool-presentation/package.json # packages/experimental/auto-review/tests/auto-review.spec.ts # packages/lsp/tool-lsp/package.json # packages/subagent/tool-subagent/tests/list-models.spec.ts # scripts/check-workspace-constraints.ts # scripts/type-equiv.manifest.json # tsconfig.base.json
description, kind
| description | kind |
|---|---|
| The Agent Client Protocol package group: the automation-only server that exposes fresh harness agents to programmatic clients over JSON-RPC stdio. | package-group |
acp/ — Agent Client Protocol automation
English | 中文
Summary
The acp group provides one package: a server that lets programs and automation run persistent DeepSeek Harness agents over the standard Agent Client Protocol. A client can create, list, resume, and close sessions; attach standard MCP servers; select model options; send text and image prompts; receive semantic updates; answer permission prompts; and cancel work without a human in the loop. The matching client for spawning such a server from another harness lives in subagent/subagent-acp. This page maps the group; the package README owns the per-package contract.
Table of Contents
Packages
| Package | Role |
|---|---|
acp/ |
Lets programs manage persistent agents over ACP, attach MCP servers, select model options, prompt and cancel work, and receive semantic updates |
Related documentation
- dsh-subagent-acp — the out-of-process ACP client that spawns and drives this server.
- ACP as an automation-only protocol — the design record for the automation contract and its wire boundaries.
- Multiplex concurrent ACP sessions over one connection — per-session isolation, ownership, and teardown decisions.
Dev Note
None.