Introduction

What is agent-hub?

agent-hub launches AI coding agents — claude, agy, codex — in long-running sessions, gives them a shared message bus, and connects that bus to your team’s chat platform via a gateway. Each agent is a role: it has its own prompt, model, skills, rules, and MCP tools.

Two flows:

• Data flow: Chat (Telegram · Discord · Slack · Webhook) → Gateway (receive · route · send) → Bus (message queue) → Agent team
• Control flow: chat commands · web app · setup app & tray · monitoring & auto-restart · workflow (tasks · runs)

The data flow carries messages; the control flow configures and monitors agents. Both flows share state managed by agent-hub.

Why this design?

• No models on the control path. Commands and routing run with no model — a model is only called when an agent is actually working.
• Single door. Each machine runs exactly one gateway, so there’s one place for authentication and logging.
• Truth from the OS. Agent liveness is read straight from the operating system, not inferred from stored state.

Read next

• Quick Start — From installer to first agent responding in chat.
• Architecture — The flow of a message from chat to agent and back.
• Gateway — The door between your agent team and where your team chats.
• Webhook integration — Connect your own systems using signed HTTP.