add-telegram-swarm

Assign separate pool bot identities to subagents in Telegram groups.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/webboty/flexclaw --skill add-telegram-swarm-webboty
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-telegram-swarm
Source: https://github.com/webboty/flexclaw/tree/main/.claude/skills/add-telegram-swarm
Command: npx skills add https://github.com/webboty/flexclaw --skill add-telegram-swarm-webboty

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables multi-agent teams to post as distinct, named bot identities in a single Telegram group so users can visually separate and identify subagent messages.

Core Features & Use Cases

  • Distinct bot identities: Assigns pool bots to subagents so each agent's messages appear from a uniquely named Telegram bot.
  • Stable per-group assignment: Maintains a stable sender→bot mapping within each group and falls back to the main bot if the pool is unavailable.
  • Integration workflow: Updates config, IPC routing, and the Telegram module to initialize send-only pool APIs, rename bots, and route sender-labeled messages.
  • Use Case: Run a researcher+coder multi-agent team where each teammate posts short, role-branded updates directly in the Telegram group.

Quick Start

Run the add-telegram-swarm skill after adding pool bot tokens and setting TELEGRAM_BOT_POOL in your environment.

Frequently Asked Questions about add-telegram-swarm

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make multiple agents send messages as separate Telegram bots in the same group?

Multi-agent teams post as distinct named bot identities by assigning separate Telegram bot pool tokens to subagents. This provides visible agent separation and role-based messaging coordination within a single Telegram group.

What do I need to set up before configuring multi-agent Telegram bot messaging?

Setting up multi-agent Telegram messaging requires an existing Telegram channel, multiple pool bot tokens with Group Privacy disabled, and TELEGRAM_BOT_POOL configured in your environment. Host IPC routing and Telegram module changes are also necessary to initialize send-only pool APIs.

How does a Telegram bot pool handle fallback when an assigned bot is unavailable?

When the Telegram bot pool is unavailable, the system falls back to using the main bot identity for messaging. This ensures continuous multi-agent coordination even if a specific pool bot token becomes unresponsive during group workflows.

Do I need to disable Group Privacy for Telegram bots to enable agent swarm messaging?

Disabling Group Privacy on your pool bot tokens is required to enable agent swarm messaging. This allows the distinct subagent bots to properly read and send role-based messages within the Telegram group environment.

Can I use this multi-agent Telegram approach for a researcher and coder team workflow?

You can use this approach for a researcher and coder multi-agent team where each teammate posts short, role-branded updates directly in the Telegram group. Each agent's messages appear from a uniquely named bot for clear visual separation.