hcom-agent-messaging
Multi-agent communication for AI coding tools. Agents message, watch, and spawn each other across terminals. Use when setting up hcom, troubleshooting delivery, or writing multi-agent scripts.
What this skill does
# 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. ```bash curl -fsSL https://github.com/aannoo/hcom/releases/latest/download/hcom-installer.sh | sh hcom claude # or: hcom gemini, hcom codex, hcom opencode, hcom kilo, hcom agy, hcom cursor-agent hcom # TUI dashboard ``` --- ## 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, bundle context for handoffs. **Observe** each other: transcripts, file edits, terminal screens, command history. **Subscribe** to each other: notify on status changes, file edits, specific events. React automatically. **Spawn**, **fork**, **resume**, **kill** each other, in any terminal emulator. run `hcom --help` for full command syntax and flags. --- ## tool support | tool | delivery | connect | |------|----------|---------| | claude code (incl. subagents) | automatic | `hcom claude` | | gemini cli (>= 0.26.0) | automatic | `hcom gemini` | | codex | automatic | `hcom codex` | | opencode | automatic | `hcom opencode` | | kilo code | automatic | `hcom kilo` | | antigravity | automatic | `hcom agy` | | cursor | automatic | `hcom cursor-agent` | | any other ai tool | manual via `hcom listen` | `hcom start` (run inside tool) | session binding (hcom transcript, hcom r/f by session id) happens on first message or first prompt for all hcom-launched tools. --- ## setup if the user invokes this skill without arguments: 1. run `hcom status` — if "command not found", install first: ```bash curl -fsSL https://github.com/aannoo/hcom/releases/latest/download/hcom-installer.sh | sh ``` 2. run `hcom hooks add` to install hooks for all detected tools 3. restart the AI tool for hooks to activate | status output | meaning | action | |---------------|---------|--------| | command not found | not installed | install via `brew install aannoo/hcom/hcom`, the curl installer above, or `pip install hcom` | | `[~] claude` | tool exists, hooks not installed | `hcom hooks add` then restart | | `[✓] claude` | hooks installed | ready | | `[✗] claude` | tool not found | install the AI tool first | --- ## troubleshooting ### "hcom not working" ```bash hcom status # check installation hcom hooks status # check hooks specifically hcom relay status # check cross-device relay ``` hooks missing? `hcom hooks add` then restart tool. still broken? ```bash hcom reset all && hcom hooks add # close all ai tool windows hcom claude # fresh start ``` ### "messages not arriving" | symptom | diagnosis | fix | |---------|-----------|-----| | agent not in `hcom list` | agent stopped or never bound | relaunch or wait for binding | | message sent but not delivered | check `hcom events --last 5` | verify @mention matches agent name/tag | | wrong agent receives message | @mention ambiguity | use `@tag-` prefix for reliable routing | | messages leaking between workflows | no thread isolation | always use `--thread` | ### intent system agents follow these rules from their bootstrap: - `--intent request` -> agent always responds - `--intent inform` -> agent responds only if useful - `--intent ack` -> agent does not respond ### sandbox / permission issues ```bash export HCOM_DIR="$PWD/.hcom" # project-local mode hcom hooks add # installs to project dir ``` --- ## workflow scripting place scripts in `~/.hcom/scripts/` as `.sh` or `.py`. run with `hcom run <name> "task"`. see `references/script-template.md` for the full annotated template, or run `hcom run docs --scripts` inside an agent. ### key rules - **never use `sleep`** — use `hcom events --wait` or `hcom listen` - **never hardcode agent names** — parse from `grep '^Names: '` in launch output - **always use `--thread`** — without it, messages leak across workflows - **always use `trap cleanup ERR INT TERM`** — orphan headless agents run indefinitely - **always use `hcom kill` for cleanup** (not `stop`) — kill also closes the terminal pane - **always forward `--name`** — hcom injects it, scripts must propagate it - **always use `--go`** on launch/kill — without it, scripts hang on confirmation prompt ### agent topologies | topology | agents | pattern | |----------|--------|---------| | worker-reviewer | 2 | worker sends result, reviewer reads transcript, sends APPROVED/FIX | | pipeline | N sequential | each stage reads previous via `hcom transcript`, signals via thread | | ensemble | N+1 (judge) | N agents answer independently, judge reads all via `hcom events --sql` | | hub-spoke | 1+N | coordinator broadcasts to `@tag-`, workers report back | | reactive | N | `hcom events sub` triggers agent actions on file edits/status changes | --- ## files | what | location | |------|----------| | database | `~/.hcom/hcom.db` | | config | `~/.hcom/config.toml` | | logs | `~/.hcom/.tmp/logs/` | | user scripts | `~/.hcom/scripts/` | with `HCOM_DIR` set, uses that path instead of `~/.hcom`. --- ## reference files | file | when to read | |------|-------------| | `references/patterns.md` | writing multi-agent scripts — 6 tested patterns with full code and real event JSON | | `references/cross-tool.md` | claude + codex + gemini + opencode collaboration details and per-tool quirks | | `references/gotchas.md` | debugging scripts — timing, message delivery, intent system, cleanup | | `references/script-template.md` | writing a new script from scratch — full template with commentary | | `references/scripts/` | 6 tested, working example scripts | --- ## more info ```bash hcom --help # all commands hcom <command> --help # command details ``` github: https://github.com/aannoo/hcom
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.