add-telegram-swarm

Route subagent messages through distinct Telegram bot identities in group chats.

401|53|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/Runchuan-BU/BioClaw --skill add-telegram-swarm-runchuan-bu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-telegram-swarm
Source: https://github.com/Runchuan-BU/BioClaw/tree/main/.claude/skills/add-telegram-swarm
Command: npx skills add https://github.com/Runchuan-BU/BioClaw --skill add-telegram-swarm-runchuan-bu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables multi-agent teams to present each subagent as a distinct bot identity inside Telegram groups so users can clearly see which role is speaking, reducing confusion in group coordination and improving traceability of agent outputs.

Core Features & Use Cases

  • Bot pool initialization: create send-only Api instances for a configurable pool of Telegram bots and initialize them from provided tokens.
  • Stable sender→bot mapping: assign pool bots round-robin and maintain stable per-group assignments keyed by groupFolder:senderName.
  • Dynamic renaming and delivery: rename pool bots using setMyName before sending and deliver messages on behalf of subagents, with fallback to the main bot when the pool is empty.
  • IPC and MCP integration: extends the MCP send_message tool to accept a sender parameter and routes IPC messages through sendPoolMessage in the host.
  • Operational guidance: updates CLAUDE.md formatting and group instructions, requires environment sync and service restart to apply changes.
  • Use Case: research teams or role-based assistant swarms that need each agent to appear with a unique, human-friendly identity in a Telegram group.

Quick Start

Add your pool bot tokens to TELEGRAM_BOT_POOL in .env, copy them to data/env/env, rebuild the project, and restart the service to initialize the bot pool and enable agent teams.

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 subagents appear as distinct Telegram bots in group chats?

To make subagents appear as distinct Telegram bots, initialize a pool of Telegram bots using separate tokens and route messages through IPC sender mapping. This assigns each subagent a stable, visible bot persona in group chats.

How does sender-to-bot mapping work for multi-agent Telegram bot pools?

Sender-to-bot mapping assigns pool bots round-robin and maintains stable per-group assignments keyed by groupFolder:senderName. This ensures each subagent consistently uses the same Telegram bot identity within a specific group chat.

Do I need specific environment variables to enable a Telegram bot pool for agent swarms?

Yes, enabling a Telegram bot pool requires setting the TELEGRAM_BOT_POOL environment variable with multiple bot tokens in your .env and data/env/env files. You must then rebuild the project and restart the service to initialize the pool.

Can I dynamically rename Telegram bots when sending messages from different subagents?

Yes, you can dynamically rename Telegram bots using the setMyName method before delivering messages. This allows each subagent's bot identity to display a human-friendly name matching its role when sending messages to the group.

What happens when the Telegram bot pool is empty and a subagent tries to send a message?

When the Telegram bot pool is empty, the system falls back to delivering messages through the main bot. This ensures subagents can still send messages to the group chat even without dedicated pool bot identities available.

How do I update the MCP send_message tool to support routing messages from multiple subagents?

To route messages from multiple subagents, extend the MCP send_message schema to accept a sender parameter and route IPC messages through the sendPoolMessage function in the host. This enables the host to direct messages to the correct pool bot.