/hcom-agent-messaging
Multi-agent communication for AI coding tools. Agents message, watch, and spawn each other across terminals. Use when setting up hcom or troubleshooting.
$ npx -y skills add aannoo/hcom --skill hcom-agent-messaging --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/hcom-agent-messaging
Context preview
The summary Claude sees to decide when to auto-load this skill.
Multi-agent communication for AI coding tools. Agents message, watch, and spawn each other across terminals. Use when setting up hcom or troubleshooting.
SKILL.md
hcom-agent-messaging.SKILL.mdname: hcom-agent-messaging
description: >
Multi-agent communication for AI coding tools. Agents message, watch,
and spawn each other across terminals. Use when setting up hcom or
troubleshooting.
hcom — multi-agent communication for AI coding tools
AI agents running in separate terminals are isolated. hcom connects them via hooks and a shared database so they can message, watch, and spawn each other in real-time.
Start an agent with `hcom` in front, then prompt normally.
Use hcom to:
- coordinate multi-agent pipelines
- run different AI CLIs as each other's subagents
- avoid copy-pasting
uv tool install hcom
hcom claude # or: hcom gemini, hcom codex, hcom opencode, hcom kilo, hcom pi, hcom omp, hcom agy, hcom cursor, hcom kimi, hcom copilot, hcom qoder, hcom grok, hcom hermes
hcom # TUI dashboard
Quickstart:
# terminal 1
hcom claude
# terminal 2
hcom codex
Prompt normally — e.g. `review what claude did and send it fixes`
---
what humans can do
tell any agent:
> send a message to claude
> when codex goes idle send it the next task
> watch gemini's file edits, review each and send feedback if any bugs
> fork yourself to investigate the bug and report back
> find which agent worked on terminal_id code, resume them and ask why it sucks
---
what agents can do
**Message** each other in real time: mid-turn or wake immediately when idle
**Observe** each other: status, transcripts, file edits, live terminal screens, command history.
**Subscribe** and notify on status changes, file edits, collisions, specific events. React automatically.
**Spawn**, **fork**, **resume**, **kill** in any terminal emulator or headless.
run `hcom --help` for full command syntax and flags.
---
Works with Claude Code, Gemini CLI, Codex, OpenCode, Kilo Code, Pi, Oh My Pi, Antigravity, Cursor, Kimi, Copilot, Qoder CLI, Grok Build, Hermes Agent, and other tools
---
setup
When this skill is invoked, first run:
hcom status
If hcom status works: run `hcom list`
If hcom list shows "Your name: <name>" where `<name>` is not "(not participating)": congratulations!
If running `hcom status` returns "command not found", install first:
uv tool install hcom
See the [hcom README](https://github.com/aannoo/hcom#install) for other install options.
If hcom status shows a list of CLI tools and you are not any of them, run `hcom start` to connect to hcom.
If you've just installed hcom now or if hcom list shows "Your name: (not participating)" and you are a tool in the hcom status list of CLI tools:
Relaunch into hcom properly for automatic message delivery and full hcom functionality. User should exit and run `hcom <tool>`. Or if you know your sessionID/ses_/thread_name: user can exit and run `hcom r <session-id>` to resume you inside hcom. See `hcom r --help`.
---
troubleshooting
"hcom not working"
hcom status # check installation
hcom hooks status # check hooks specifically
hcom relay status # check cross-device relay
still broken?
hcom reset all # backup config/db + reset it
hcom claude # fresh start
still broken after that?
git clone https://github.com/aannoo/hcom.git
cd hcom
Read code and figure out what is going on.
sandbox / permission issues
Use project-local hcom state when the normal hcom directory is unavailable:
HCOM_DIR=$PWD/.hcom hcom <tool>
files
| what | location | |------|----------| | database | `~/.hcom/hcom.db` | | config | `~/.hcom/config.toml` | | env | `~/.hcom/env` | | logs | `~/.hcom/.tmp/logs/` | | user scripts | `~/.hcom/scripts/` |
---
more info
hcom --help
hcom <command> --help
hcom run docs --scripts # script authoring info
Github: https://github.com/aannoo/hcom
Read more
name: hcom-agent-messaging description: > Multi-agent communication for AI coding tools. Agents message, watch, and spawn each other across terminals. Use when setting up hcom or troubleshooting.
hcom — multi-agent communication for AI coding tools
AI agents running in separate terminals are isolated. hcom connects them via hooks and a shared database so they can message, watch, and spawn each other in real-time.
Start an agent with `hcom` in front, then prompt normally.
Use hcom to:
- coordinate multi-agent pipelines
- run different AI CLIs as each other's subagents
- avoid copy-pasting
uv tool install hcom hcom claude # or: hcom gemini, hcom codex, hcom opencode, hcom kilo, hcom pi, hcom omp, hcom agy, hcom cursor, hcom kimi, hcom copilot, hcom qoder, hcom grok, hcom hermes hcom # TUI dashboard
Quickstart:
# terminal 1 hcom claude # terminal 2 hcom codex
Prompt normally — e.g. `review what claude did and send it fixes`
---
what humans can do
tell any agent:
> send a message to claude
> when codex goes idle send it the next task
> watch gemini's file edits, review each and send feedback if any bugs
> fork yourself to investigate the bug and report back
> find which agent worked on terminal_id code, resume them and ask why it sucks
---
what agents can do
**Message** each other in real time: mid-turn or wake immediately when idle
**Observe** each other: status, transcripts, file edits, live terminal screens, command history.
**Subscribe** and notify on status changes, file edits, collisions, specific events. React automatically.
**Spawn**, **fork**, **resume**, **kill** in any terminal emulator or headless.
run `hcom --help` for full command syntax and flags.
---
Works with Claude Code, Gemini CLI, Codex, OpenCode, Kilo Code, Pi, Oh My Pi, Antigravity, Cursor, Kimi, Copilot, Qoder CLI, Grok Build, Hermes Agent, and other tools
---
setup
When this skill is invoked, first run:
hcom status
If hcom status works: run `hcom list`
If hcom list shows "Your name: <name>" where `<name>` is not "(not participating)": congratulations!
If running `hcom status` returns "command not found", install first:
uv tool install hcom
See the [hcom README](https://github.com/aannoo/hcom#install) for other install options.
If hcom status shows a list of CLI tools and you are not any of them, run `hcom start` to connect to hcom.
If you've just installed hcom now or if hcom list shows "Your name: (not participating)" and you are a tool in the hcom status list of CLI tools:
Relaunch into hcom properly for automatic message delivery and full hcom functionality. User should exit and run `hcom <tool>`. Or if you know your sessionID/ses_/thread_name: user can exit and run `hcom r <session-id>` to resume you inside hcom. See `hcom r --help`.
---
troubleshooting
"hcom not working"
hcom status # check installation hcom hooks status # check hooks specifically hcom relay status # check cross-device relay
still broken?
hcom reset all # backup config/db + reset it hcom claude # fresh start
still broken after that?
git clone https://github.com/aannoo/hcom.git cd hcom
Read code and figure out what is going on.
sandbox / permission issues
Use project-local hcom state when the normal hcom directory is unavailable:
HCOM_DIR=$PWD/.hcom hcom <tool>
files
| what | location | |------|----------| | database | `~/.hcom/hcom.db` | | config | `~/.hcom/config.toml` | | env | `~/.hcom/env` | | logs | `~/.hcom/.tmp/logs/` | | user scripts | `~/.hcom/scripts/` |
---
more info
hcom --help hcom <command> --help hcom run docs --scripts # script authoring info
Github: https://github.com/aannoo/hcom
Hook your coding agents together CLI tool that agents use to message, watch, and spawn each other across terminals. Start an agent with hcom in front, then prompt normally.