中文 | English

ACP Protocol Surface Guide

Scope: this guide applies to src/crates/interfaces/acp.

bitfun-acp owns the Agent Client Protocol surface over the assembled product runtime. Keep ACP protocol/client details here or in app-surface adapters; share only stable capability facts through contract crates.

Guardrails

• Remote ACP workspaces reuse local ACP client configuration. Preserve the manager, remote shell probing, remote capability store, and workspace menu availability semantics when changing ACP client behavior.
• ACP config persistence, remote probing, timeout policy, and workspace surface selection are ACP/app-surface behavior. Do not move them into core-types, runtime-ports, or agent-tools.
• ACP external-agent tool naming, schema, validation, presentation, and result shape are portable contracts owned by bitfun-agent-tools; ACP should call those helpers instead of redefining them locally.
• If a future contract is needed, make it observational: environment identity, capability facts, and request/response DTOs only.

Verification

cargo check -p bitfun-acp
cargo test -p bitfun-acp