Problem

Currently, delegate_task inherits acp_command and acp_args from the parent agent with no override option:

effective_acp_command = getattr(parent_agent, "acp_command", None)
effective_acp_args = list(getattr(parent_agent, "acp_args", []) or [])

This means:

• If parent is running via Discord/Telegram/CLI (no ACP), children cannot use ACP transport
• You cannot spawn a child with a different transport than the parent

Use Case

From Discord, I want to delegate a task to a child agent running over ACP (e.g., claude --acp --stdio or copilot --acp --stdio) to get a different model/personality in a sub-thread.

Specific Use Case: Claude Code Max Subscription

I have a Claude Code Max OAuth subscription (claude.ai/code). This gives me access to the Claude Code CLI (claude --acp --stdio) which provides:

• Full agentic loop with file editing, terminal, reasoning
• Uses my Max subscription quota (not API credits)
• Native ACP protocol support

Current workflow in OpenClaw:

"can you spawn claude acp in sub thread"

Results in a new Discord thread with Claude Opus 4.6 running autonomously via ACP.

What I want in Hermes:

delegate_task(
    goal="Refactor this codebase for better testability",
    acp_command="claude",  # Uses my Claude Code Max subscription
    acp_args=["--acp", "--stdio"],
)

This would:

1. Spawn Claude Code subprocess via ACP protocol
2. Claude Code uses Max plan quota (OAuth-authenticated)
3. Child runs autonomous agentic loop
4. Returns summary to parent

Proposed Solution

Add acp_command and acp_args parameters to delegate_task tool schema:

def _build_child_agent(
    ...
    override_acp_command: str = None,
    override_acp_args: list[str] | None = None,
    ...
):
    effective_acp_command = override_acp_command or getattr(parent_agent, "acp_command", None)
    effective_acp_args = list(override_acp_args or getattr(parent_agent, "acp_args", []) or [])

Tool schema addition:

{
  "name": "acp_command",
  "type": "string",
  "description": "Override ACP command for child (e.g., 'claude', 'copilot'). If set, child uses ACP transport."
},
{
  "name": "acp_args",
  "type": "array",
  "items": {"type": "string"},
  "description": "ACP command arguments (default: ['--acp', '--stdio'])"
}

Current Workarounds

Related

• Feature: Agent Client Protocol (ACP) Server Mode — Run Hermes in Zed, JetBrains, Neovim, Toad & Any ACP-Compatible Editor #569 — ACP Server Mode (running Hermes as ACP server)
• Feature: A2A (Agent-to-Agent) Protocol Support — Remote Agent Discovery, Communication & Interoperability #514 — A2A Protocol Support (agent-to-agent communication)
• PR feat: multi-agent architecture — named agents with routing, tool policies, and isolated workspaces #896 — Multi-agent architecture (named agents with routing)

Related

• Feature: Agent Client Protocol (ACP) Server Mode — Run Hermes in Zed, JetBrains, Neovim, Toad & Any ACP-Compatible Editor #569 — ACP Server Mode (running Hermes as ACP server)
• feat: restore ACP server implementation that was missed from PR #949 #1254 — ACP server implementation restored (commit 25481d4) — Hermes as server, opposite direction from this request
• Feature: A2A (Agent-to-Agent) Protocol Support — Remote Agent Discovery, Communication & Interoperability #514 — A2A Protocol Support (agent-to-agent communication)
• PR feat: multi-agent architecture — named agents with routing, tool policies, and isolated workspaces #896 — Multi-agent architecture (named agents with routing)