Hcom Agent Messaging logo

Hcom Agent Messaging

Community
aannoo
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.

Overview

Publisheraannoo
Repositoryhcom
Skill namehcom-agent-messaging
Stars
566
Forks
86
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by aannoo on GitHub. Read the source before you install it.

Installation

Install the Hcom Agent Messaging AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/aannoo/hcom/tree/main/skills/hcom-agent-messaging
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/aannoo/hcom.git /tmp/hcom
mkdir -p .claude/skills
cp -r /tmp/hcom/skills/hcom-agent-messaging .claude/skills/hcom-agent-messaging
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Hcom Agent Messaging in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Hcom Agent Messaging on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Hcom Agent Messaging is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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
bash
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              # TUI dashboard

Quickstart:

bash
# 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, and other tools


setup

When this skill is invoked, first run:

bash
hcom status

If hcom status works: run hcom list

If hcom list shows "Your name: " where <name> is not "(not participating)": congratulations!

If running hcom status returns "command not found", install first:

bash
uv tool install hcom

See the hcom README 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"

bash
hcom status          # check installation
hcom hooks status    # check hooks specifically
hcom relay status    # check cross-device relay

still broken?

bash
hcom reset all # backup config/db + reset it
hcom claude          # fresh start

still broken after that?

bash
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:

bash
HCOM_DIR=$PWD/.hcom hcom <tool>

files

whatlocation
database~/.hcom/hcom.db
config~/.hcom/config.toml
env~/.hcom/env
logs~/.hcom/.tmp/logs/
user scripts~/.hcom/scripts/

more info

bash
hcom --help
hcom <command> --help
hcom run docs --scripts   # script authoring info

Github: https://github.com/aannoo/hcom

Frequently asked questions

What does the Hcom Agent Messaging AI skill do?

Multi-agent communication for AI coding tools. Agents message, watch, and spawn each other across terminals. Use when setting up hcom or troubleshooting.

Why use Hcom Agent Messaging on TypingMind?

Because you install it once and use it with any model. Hcom Agent Messaging is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Hcom Agent Messaging in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/aannoo/hcom/tree/main/skills/hcom-agent-messaging. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Hcom Agent Messaging?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Hcom Agent Messaging?

As many as you like. As long as a model supports skills, you can use Hcom Agent Messaging with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Hcom Agent Messaging AI skill free?

Yes. It is published on GitHub by aannoo under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇