Add ACP (Agent Client Protocol) support to Capacities Chat

Capacities already has excellent MCP support, allowing external agents to access workspace data. ACP would complement this by letting Capacities Chat become a frontend for external agents like Claude Code, Codex, Gemini CLI, Hermes, OpenCode, or custom agents.

Unlike BYOK (Bring Your Own Key), which only lets users choose the model/provider while Capacities still controls the agent behavior, ACP would let users bring their own agent runtime with its own planning, tools, memory, long-running sessions, approvals, and workflows.

This would make Capacities an agent-native workspace where users can use their preferred AI agent directly inside Capacities instead of switching to a terminal or another application. The ideal architecture would be:

Capacities Chat ↔ ACP ↔ External Agent ↔ MCP ↔ Capacities Workspace

In short: BYOK lets users bring their own model; ACP lets users bring their own agent.

https://agentclientprotocol.com/get-started/introduction