add-telegram-swarm

Route agent messages through a Telegram bot pool with stable per-group sender mapping.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many multi-agent workflows in Telegram appear as a single bot, making it hard for users to distinguish which subagent produced each message. This Skill makes subagents appear as distinct bot identities in Telegram groups so team outputs are clear, scannable, and attributable.

Core Features & Use Cases

  • Multi-bot agent teams: Assign subagents to a pool of send-only Telegram bots that are renamed to match agent roles so messages appear from separate identities.
  • Stable per-group mapping and fallbacks: Round-robin assignment with stable sender→bot mapping during runtime and fallback to the main bot if no pool is configured.
  • Integration points: Adds TELEGRAM_BOT_POOL environment support, initializes Grammy Api instances for pool bots, extends the MCP send_message tool with a sender parameter, and routes IPC messages through the pool.
  • Use Case: Run a researcher+coder agent team in a single Telegram group where each agent posts concise, role-labeled updates via dedicated bot identities.

Quick Start

Ask the assistant to enable multi-bot agent teams for your Telegram group by providing the pool bot tokens and confirming the target group folder.

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

To make subagents appear as separate bots in Telegram, you route messages through a pool of send-only bot identities. The pool bots are renamed to match agent roles, ensuring team outputs are clear and attributable.

Can I use multiple Telegram bots for a single agent team workflow?

Yes, you can use multiple Telegram bots for a single agent team by assigning subagents to a token-based bot pool. This allows a researcher and coder agent to post role-labeled updates via dedicated identities.

How to route IPC messages to distinct Telegram bot identities?

You route IPC messages to distinct Telegram identities by extending the MCP send_message tool with a sender parameter. This parameter directs the message through the corresponding bot in the initialized pool.

Does multi-bot Telegram routing require a specific deployment environment?

Multi-bot Telegram routing applies to self-hosted NanoClaw deployments. It relies on Grammy API instances for pool bots and requires a TELEGRAM_BOT_POOL environment configuration to function.

What happens if no bot pool is configured for Telegram agent teams?

If no bot pool is configured for Telegram agent teams, the system uses a fallback mechanism. All subagent messages are routed through the main bot identity instead of distinct senders.

How is sender-to-bot mapping maintained during Telegram group conversations?

Sender-to-bot mapping is maintained using stable round-robin assignment during runtime. This ensures a subagent consistently posts as the same renamed bot identity within a specific Telegram group.