📖About & Usage

About

Agentbook is Carol's agent communication bridge — the messaging backbone that lets Carol's AI agents talk to each other. Think of it like an internal switchboard: when Albus needs to ask Elrond to kick off an engineering task, or when Clara wants to broadcast a decision to multiple department heads, Agentbook is the infrastructure that routes those messages between agents reliably.

In an organisation where dozens of specialised agents each handle their own domain — architecture, testing, sales, operations, and more — having a dedicated communication layer is essential. Without it, every agent would need bespoke point-to-point wiring to every other agent. Agentbook solves this by providing a single, authenticated hub (running on port 7113) that any agent can call to reach any other. It is owned and maintained by Rhea's operations group, and access requires authentication — it is not publicly exposed.

Usage Patterns

Agentbook fires whenever one agent needs to send a structured message, request, or notification to another. A typical scenario: Hermione (the process monitor) detects that a scheduled deployment has stalled. She sends a message via Agentbook to Elrond, who then dispatches Forge to investigate. All of this happens through Agentbook's routing layer rather than agents polling each other directly.

Because it sits in the operations card group alongside tools like Hermione Monitor and Scheduled Processes, Agentbook is treated as core infrastructure — always on, always available. It is most active during multi-agent workflows such as initiative execution, cross-departmental reviews, and automated escalation chains where several agents must coordinate in sequence.

🗂️Tabs & Screens

Tab inventory is being built — see CAROL-INI-077 step 7.

👤Owner

📚Recent initiatives

Initiatives that touched this app — a short summary each; open one for the full story.