mirror of
https://github.com/deepseek-ai/deepseek-harness.git
synced 2026-09-12 04:01:20 +00:00
_Kerman
25b0c943ce
# Conflicts: # .agents/notes/implemented/architecture/2026-08-04-draft-provider-endpoint-interrogation.i18n.yaml # .agents/notes/implemented/architecture/2026-08-04-draft-provider-endpoint-interrogation.md # .agents/notes/implemented/architecture/2026-08-04-draft-provider-endpoint-interrogation.zh.md # .agents/notes/implemented/feature/2026-08-06-continuable-subagent-interrupt.i18n.yaml # .agents/notes/implemented/feature/2026-08-06-continuable-subagent-interrupt.md # .agents/notes/implemented/feature/2026-08-06-continuable-subagent-interrupt.zh.md # .agents/notes/implemented/process/2026-07-20-gui-testing-system.i18n.yaml # .agents/notes/implemented/process/2026-07-20-gui-testing-system.md # .agents/notes/implemented/process/2026-07-20-gui-testing-system.zh.md
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.