Top AI Repos — open-source AI, indexed and scored
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Production-tested templates for deploying multi-agent AI teams on OpenClaw with Telegram supergroup integration. 10 agent personalities, shared context workflows, bot-to-bot communication, and step-by-step AI-readable setup instructions. Built from a live 10-agent setup.
| Date | Stars |
|---|---|
| 2026-07-31 | 394 |
| 2026-08-02 | 394 |
| 2026-08-06 | 394 |
Today
— stars today
This week
— stars this week
This month
— stars this month
Momentum
0.0
growth rate 0.00%/day
# OpenClaw Agents — Multi-Agent Telegram Supergroup Templates
> **Production-tested templates for building AI agent teams on [OpenClaw](https://openclaw.sh) with Telegram supergroup integration.**
This is an **OpenClaw-specific** project. These templates are designed to run on the OpenClaw platform — they use OpenClaw's agent system, workspace structure, session management, `sessions_send` for bot-to-bot communication, and Telegram channel bindings. If you're not running OpenClaw, these won't work out of the box.
Built from a real production setup running 10 autonomous agents coordinated through a Telegram supergroup with dedicated topic channels. Each agent has its own bot, personality, workspace, and domain expertise.
---
## Credits & Inspiration
Agent personality patterns and the concept of specialized AI agent divisions are inspired by **[The Agency](https://github.com/msitarzewski/agency-agents)** by [@msitarzewski](https://github.com/msitarzewski) — a collection of 55+ specialized AI agent personalities built for Claude Code. Great resource for agent design philosophy, personality crafting, and workflow patterns regardless of what platform you run.
What we build here is different: the **operational infrastructure** for running those kinds of agents as a live, coordinated team on OpenClaw — with Telegram supergroups, shared context files, bot-to-bot triggers, cron schedules, topic-based team channels, and structured escalation chains.
---
## What Is This?
A complete template kit for deploying a multi-agent team on **OpenClaw + Telegram**:
- **SOUL.md templates** — Agent personality and behavior definitions
- **IDENTITY.md templates** — Agent metadata and capabilities
- **Workspace templates** — Shared context, memory, and coordination files
- **openclaw.json snippets** — Configuration for agents, bindings, channels, and teams
- **AI Instructions** — Step-by-step setup guide written for AI agents to follow
- **Architecture docs** — How agents communicate, escalate, and share context
---
## Architecture Overview
```
┌──────────┐
│ You 👑 │
└────┬─────┘
│
┌────▼─────┐
│Lead Agent│ Orchestrator
└────┬─────┘
┌──────────────┼──────────────┐
│ │ │
┌─────▼─────┐ ┌────▼────┐ ┌─────▼─────┐
│ RESEARCH │ │ BUILD │ │ MARKET │
│ Team │ │ Team │ │ Team │
└─────┬─────┘ └────┬────┘ └─────┬─────┘
│ │ │
Research + Code → QA → Content +
Analytics Deploy Community
```
### Key Concepts
- **Three Telegram routing models** — multi-bot routing, native topic routing, and DM forum topics
- **Multi-bot routing** — Each agent has its own Telegram bot token and visible identity
- **Native topic routing** — One Telegram bot can route different topics to different internal agents via `topics.<id>.agentId`
- **One topic per team** — Teams share a topic channel in a supergroup
- **Primary + Secondary agents** — Primary owns the topic; secondary responds when mentioned or triggered
- **Shared context via files** — Agents coordinate through shared markdown files, not APIs
- **Structured escalation** — Clear rules for when to escalate up the chain
### Important Telegram Routing Caveat
In native topic routing, `agentId` controls the **internal OpenClaw agent** that handles the message — workspace, memory, tools, prompt, model, session.
It does **not** control the **visible Telegram bot identity**.
So this:
```json5
"13": { agentId: "connor" }
```
means Topic 13 is handled by the `connor` agent internally, but replies still come from whichever Telegram account is attached to that group/topic (often the default/orchestrator bot).
Use this rule of thumb:
- **Want one visible bot with many internal specialist brains?** Use native topic routingExcerpt of 11,320 characters
Read on GitHubWould you bet a product on this? Bounded 0–100 and slow moving.
matched fp:0f7f30600846edea, name:multi-agent, desc:multi-agent, name:multi agent