07afa717ac
Direct messages between agents through the hub — architect↔agent and agent↔agent
questions, clarifications and pings that handoffs/memories don't cover. Built as
MCP tools so kimi + codex get it too (not Claude-only), plus REST + CLI.
- Message entity (MSG-NNNN): schema, counter, messages/ dir, messageService
(createMessage / listInbox / listMessages / markMessageRead).
- REST: POST /messages, GET /messages[?agent&unread], POST /messages/:id/read,
with SSE emit. fsWatch + statusRefresh wired ('message' events; status skips them).
- MCP: agenthub_message {from,to,text,taskId?} + agenthub_inbox {agent,unreadOnly?}.
agenthub_work now surfaces + drains unread messages and wakes on message events,
so an agent sees messages inside its work loop. (18 tools total.)
- CLI: `agenthub message <to> <text> --from <agent>` + `agenthub inbox --agent`.
watch stream shows "Message" events (architect-visible).
- Architect-visible by design: the hub stays the coordination point.
Bump 0.7.5 -> 0.8.0.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
AgentHub
Local coordination layer for AI coding agents.
Install
AgentHub is not yet published to npm. Clone the repository, build it, and link it globally:
git clone https://git.rebreak.org/chahine/agenthub.git
cd agenthub
pnpm install
pnpm build
npm link
After npm link, the agenthub command is available everywhere.
Quick Start
agenthub init
agenthub task create --title "Implement DNS cache" --role implementer
agenthub handoff create --fromRole architect --toRole implementer
agenthub status --update
Supported Agents
- Claude Code
- Codex CLI
- Kimi Code CLI
Network Mode
AgentHub can expose a project to other machines on the same network. Discovery is automatic: as soon as the host broadcasts, a client can find it without knowing the IP address.
On the host machine (e.g. Mac):
cd my-project
agenthub init
agenthub server start --host 0.0.0.0 --port 3377
On another machine (e.g. Windows) run init and accept the discovered server:
cd my-project
agenthub init # asks to connect to the LAN server it found
agenthub task create --title "Windows task" --role implementer
agenthub status
For non-interactive setup, let init discover the server automatically:
agenthub init --server auto
After init, every command automatically talks to the configured server. You can still override it per command with --server http://<ip>:3377 or via the AGENTHUB_SERVER environment variable.
The init --server step only stores the server URL locally; it does not create a second project. The host machine keeps the single source of truth.
License
MIT