The Agent Client Protocol (ACP) is a JSON-RPC standard that lets different AI coding agents talk to each other. Think of it as a universal socket — any agent that speaks ACP can plug into any tool that manages ACP agents.
Hermes Agent ships an ACP adapter (hermes acp), version 0.19.0. That’s the plumbing. The interesting part is what you can plug it into.
hcom — Cross-Agent Messaging
hcom is a cross-agent messaging layer (SQLite-based). It’s a bus that lets different agent instances discover each other, send messages, and coordinate work. Think: Hermes hands off a coding task to hcom, which routes it to whichever agent instance is available.
Links & Stats 👉 https://github.com/aannoo/hcom
![]()
![]()
![]()
The open PR adds a full Hermes ACP delivery loop:
- Raw PTY injection — Hermes gets a pseudo-terminal to interact with, so it can run commands and get output in real-time
- Hermes transcript parser — hcom understands Hermes’s conversation format, so it can extract context, decisions, and artifacts
- Integration wiring — config, UI, and session management so hcom treats Hermes as a first-class peer alongside Claude Code, Codex, and others
This makes hcom → Hermes a real path: hcom routes work to Hermes, Hermes executes, hcom collects the results.
Kandev — Multi-Agent Orchestration Dashboard
Kandev is a kanban-based development environment for orchestrating multiple AI agents. Think: a web UI where you create tasks, assign them to different agents (Claude Code, Codex, Copilot, Gemini, Hermes), review their output, and manage PRs — all from one dashboard.
Links & Stats 👉 https://github.com/kdlbs/kandev
![]()
![]()
![]()
The merged integration (PR #2089, v0.83.0) adds Hermes to Kandev’s ACP agent roster:
- Kandev can launch Hermes as a task executor
- Tasks appear in the kanban board alongside other agents’ work
- Output lands in the integrated workspace — file editor, terminal, git changes
Why This Matters
A single agent running in a terminal is powerful. An agent that can be dispatched, tracked, and reviewed from an orchestration layer is something else entirely.
The pipeline looks like this:
Kandev (orchestration dashboard)
└→ dispatches task via ACP
└→ hcom (cross-agent message bus)
└→ routes to Hermes agent
└→ Hermes executes in isolated workspace
└→ results flow back up the chain
Each layer does one thing well:
- Kandev — task management, review gates, PR workflow
- hcom — inter-agent routing, message persistence, session management
- Hermes — tool execution, memory, cron, platform integrations
No single tool tries to do everything. The ACP protocol is the glue.
The State of Play
- hcom Hermes ACP PR — open, under review. Adds delivery loop, PTY injection, transcript parsing
- Kandev Hermes ACP integration — merged in v0.83.0. Hermes is a first-class agent in the dashboard
- Hermes ACP adapter — ships with Hermes, version 0.19.0, check passes clean
The ecosystem is real and growing. Hermes sits alongside Claude Code, Codex, and Copilot in both tools’ agent rosters — not as a toy, but as a production-grade ACP peer.
If you’re running Hermes and want orchestration, the path is there. Pull hcom, fire up Kandev, and wire them together. The protocol handles the rest.