hermes - 💡(How to fix) Fix [Feature Request] Kanban: native acp_command support for third-party agent backends [1 participants]

Summary

Allow Kanban tasks to be dispatched directly to third-party ACP-compatible agents (Claude Code, Codex, OpenCode) without requiring an intermediate Hermes profile wrapper.

Motivation

• delegate_task already supports acp_command / acp_args to route subtasks to external agents like Claude Code (claude --acp --stdio)
• Kanban currently only dispatches to Hermes profiles — to use Claude Code as a worker, you need a profile whose sole job is to call claude -p
• This adds unnecessary overhead and an extra layer of indirection

Proposed Solution

Add --acp-command and --acp-args options to hermes kanban create (and the corresponding kanban_create() tool), so the dispatcher can spawn the worker via ACP transport instead of launching a Hermes profile.

Example:

hermes kanban create "Implement rate limiter" \
  --assignee claude-code \
  --acp-command claude \
  --acp-args "--acp --stdio" \
  --skill test-driven-development \
  --workspace worktree

Alternatively, allow profiles to declare acp_command in their config.yaml so any task assigned to that profile automatically routes through ACP:

# ~/.hermes-claude-coder/config.yaml
acp_command: claude
acp_args: ["--acp", "--stdio"]

Use Case

Pre-define specialist roles (researcher, backend-eng, reviewer) where some are Hermes-native and others delegate to Claude Code or Codex — all managed uniformly through the Kanban board.