autoresearchclaw-acp-protocol-uses-claude-as-llm-backend
AutoResearchClaw has built-in ACP (Agent Client Protocol) support configurable via ‘llm.acp.agent: claude’. When ACP mode is active, AutoResearchClaw delegates its LLM calls through Claude Code rather than calling APIs directly, enabling use of the existing Max subscription with zero separate API cost. However, ACP is designed for LLM delegation not orchestration — it gives less granular control over individual pipeline stages compared to an MCP server wrapper.
Related
- docker
- enterprise-capability-expansion-5-pillars-from-digital-employee-analysis
- mcp-server-preferred-over-cli-acp-for-researchclaw-invocatio
- 2026-04-04-oracle-001-self-architecture-analysis
- oracle
- acp-protocol-wrong-pattern-for-oracle-orchestration
- autoresearchclaw-acp-llm-delegation-available
- acp-protocol-designed-for-llm-delegation-not-orchestration
- autoresearchclaw-acp-protocol-delegates-llm-calls-through-cl
- autoresearchclaw-acp-protocol-claude-code-native-integration
- autoresearchclaw-native-acp-supports-claude-as-backend
- autoresearchclaw-acp-protocol-for-claude-code-integration
- autoresearchclaw-acp-protocol-supports-claude-code