Telegram pairing is just two values in this agent's .env:
the bot token from @BotFather and the chat ID the bot
should reply to. Changes take effect after a gateway restart (button below).
/newbot. BotFather asks for a display name, then a username ending in bot (e.g. nellobyte_agent2_bot). Username must be globally unique — pick one tied to the agent.123456789:ABCdef-Ghi…. Copy it. Treat it like a password: anyone with the token can post as the bot./mybots → pick the bot → API Token to retrieve or regenerate the existing token./start). Without this first message, Telegram won't expose the chat to the bot's API.https://api.telegram.org/bot<TOKEN>/getUpdates<TOKEN>)."chat":{"id":NNNNNNNN,…} in the JSON. That number is the chat ID. Personal chats are positive integers (e.g. 8059732436); group/supergroup chats are negative (e.g. -1001234567890); public channels can be referenced as @channelname.getUpdates. The chat.id will be the group's ID.getMe to confirm the token before persisting; on success you'll see the bot's @username + first name in the confirm dialog..env at boot, so token/chat-ID changes only take effect after the restart.@-mention them or are replies to their messages. To let the bot see all group messages, send /setprivacy to BotFather, pick the bot, choose Disable.After changing token or chat ID, restart this agent's gateway so the Telegram channel reloads with the new values. The active session reconnects within ~10 seconds.