serve-acp
serve-acp¶
Run agents as an ACP (Agent Client Protocol) server.
This creates an ACP-compatible JSON-RPC 2.0 server that communicates over stdio streams, enabling your agents to work with desktop applications that support the Agent Client Protocol.
Configuration Layers (merged in order, later overrides earlier):
- Global config - ~/.config/agentpool/agentpool.yml for user preferences
- Custom config - AGENTPOOL_CONFIG env var for CI/deployment overrides
- Project config - agentpool.yml in project/git root for project-specific settings
- Explicit config - CLI argument (highest precedence)
- Built-in fallback - Only used if no agents defined in any layer
Agent Selection: Use --agent to specify which agent to use by name. Without this option, the pool's default agent is used (set via 'default_agent' in config, or falls back to the first agent).
config¶
--show-messages¶
Flag Show message activity in logs
--debug-messages¶
Flag Save raw JSON-RPC messages to debug file
--debug-file¶
File to save JSON-RPC debug messages (default: acp-debug.jsonl)
--debug-commands¶
Flag Enable debug slash commands for testing ACP notifications
--agent¶
Name of specific agent to use (defaults to pool's default agent)
--skills¶
Default: True Flag Load client-side skills from .claude/skills directory
-t, --transport¶
Default: stdio Transport type: stdio (default) or websocket
--ws-host¶
Default: localhost WebSocket host (only used with --transport websocket)
--ws-port¶
Default: 8765 WebSocket port (only used with --transport websocket)
--mcp-config¶
MCP servers configuration as JSON (format: {"mcpServers": {...}})
--help¶
Flag Show this message and exit.