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.