ScuttleBot
docs: add who is it for section, call out OpenClaw swarm use case
Commit
b379cdecc32bc1722865f250d260f10f32e737a9f66ddf87c5d074adca873245
Parent
bb06ddc2c364041…
1 file changed
+11
+11
| --- README.md | ||
| +++ README.md | ||
| @@ -40,10 +40,21 @@ | ||
| 40 | 40 | |
| 41 | 41 | ### Why not RabbitMQ? |
| 42 | 42 | |
| 43 | 43 | Wrong tool. RabbitMQ is designed for guaranteed delivery workflows. It is operationally heavy, not human observable without a management UI, and not designed for real-time coordination between actors. |
| 44 | 44 | |
| 45 | +--- | |
| 46 | + | |
| 47 | +## Who is it for? | |
| 48 | + | |
| 49 | +Anyone running fleets of AI agents that need to coordinate, report activity, and stay observable. | |
| 50 | + | |
| 51 | +- **[OpenClaw](https://openclaw.ai) swarms** — run multiple OpenClaw agents and give them a shared backplane to coordinate over. The MCP server makes it plug-in ready with no custom integration code. | |
| 52 | +- **Claude Code / Gemini / Codex fleets** — multiple coding agents working on the same project, sharing context in real time | |
| 53 | +- **Ops and monitoring agents** — agents watching infrastructure, triaging alerts, escalating to humans — all visible in a single IRC channel | |
| 54 | +- **Any multi-agent system** where humans need to see what's happening without a custom dashboard | |
| 55 | + | |
| 45 | 56 | --- |
| 46 | 57 | |
| 47 | 58 | ## How it works |
| 48 | 59 | |
| 49 | 60 | scuttlebot manages an [Ergo](https://ergo.chat) IRC server. Users configure scuttlebot — never Ergo directly. |
| 50 | 61 |
| --- README.md | |
| +++ README.md | |
| @@ -40,10 +40,21 @@ | |
| 40 | |
| 41 | ### Why not RabbitMQ? |
| 42 | |
| 43 | Wrong tool. RabbitMQ is designed for guaranteed delivery workflows. It is operationally heavy, not human observable without a management UI, and not designed for real-time coordination between actors. |
| 44 | |
| 45 | --- |
| 46 | |
| 47 | ## How it works |
| 48 | |
| 49 | scuttlebot manages an [Ergo](https://ergo.chat) IRC server. Users configure scuttlebot — never Ergo directly. |
| 50 |
| --- README.md | |
| +++ README.md | |
| @@ -40,10 +40,21 @@ | |
| 40 | |
| 41 | ### Why not RabbitMQ? |
| 42 | |
| 43 | Wrong tool. RabbitMQ is designed for guaranteed delivery workflows. It is operationally heavy, not human observable without a management UI, and not designed for real-time coordination between actors. |
| 44 | |
| 45 | --- |
| 46 | |
| 47 | ## Who is it for? |
| 48 | |
| 49 | Anyone running fleets of AI agents that need to coordinate, report activity, and stay observable. |
| 50 | |
| 51 | - **[OpenClaw](https://openclaw.ai) swarms** — run multiple OpenClaw agents and give them a shared backplane to coordinate over. The MCP server makes it plug-in ready with no custom integration code. |
| 52 | - **Claude Code / Gemini / Codex fleets** — multiple coding agents working on the same project, sharing context in real time |
| 53 | - **Ops and monitoring agents** — agents watching infrastructure, triaging alerts, escalating to humans — all visible in a single IRC channel |
| 54 | - **Any multi-agent system** where humans need to see what's happening without a custom dashboard |
| 55 | |
| 56 | --- |
| 57 | |
| 58 | ## How it works |
| 59 | |
| 60 | scuttlebot manages an [Ergo](https://ergo.chat) IRC server. Users configure scuttlebot — never Ergo directly. |
| 61 |