Telegram integration is primarily useful for OpenClaw. Other agent packs (Claude Code, Codex CLI, Hermes, Pi, IronClaw, Kiro CLI) are terminal-based tools. Some have Telegram support — check their specific bootstrap sections — but the full interactive chat experience is an OpenClaw feature.
Prerequisites
Before running the Telegram bootstraps, you need:- A Telegram account
- A Telegram bot token from BotFather (free — takes about 2 minutes to create)
- The essential bootstraps already run on your agent
Available Telegram bootstraps
BOOTSTRAP-TELEGRAM
Sets up your agent as a Telegram bot for direct messages. Covers creating the bot with BotFather, storing the token in AWS Secrets Manager, configuring the agent, and setting up allowlists so only you can interact with it.Run this first.
BOOTSTRAP-TELEGRAM-GROUP
Configures your agent to participate in a private Telegram group. Useful when you’re running multiple Lowkey instances across different AWS accounts and want to broadcast commands to all of them from one place.Run this only after
BOOTSTRAP-TELEGRAM is working.Run the Telegram bootstraps
Set up direct message integration
Paste this into your agent chat:The agent walks you through creating the bot with BotFather, storing your token securely, and configuring the Telegram channel. At the end, send your bot a message — you should get a response within a few seconds.
Verify DMs are working
Before setting up group chat, confirm that direct messages work end-to-end. Send your bot a simple message like “status” and make sure you get a reply.
Security considerations
Both Telegram bootstraps configure allowlists by default — your agent only responds to your Telegram user ID, not to anyone who messages the bot. Keep this in place. After setup, consider running/setjoingroups → Disable in BotFather to prevent your bot from being added to unauthorized groups. Re-enable it temporarily if you need to join a new group.
How the multi-agent group works
When you have multiple Lowkey instances in a private Telegram group, you can broadcast to all of them at once or target a specific one:@fleet check GuardDuty— all agents in the group respond@all status— all agents respond- Reply to a specific agent’s message — only that agent responds
@bot_username do X— only that specific agent responds