I Added Telegram to My AI Agent. One Config Line Was Silently Eating All My Responses.

I Added Telegram to My AI Agent. One Config Line Was Silently Eating All My Responses. When you run an AI agent that already has a working WhatsApp channel, adding Telegram feels like it should be trivially easy. Pair a bot, enable the channel, done. And it mostly was — except for one config flag that quietly swallowed every streaming response, and took a morning session to untangle. Here's the full story. The Setup My AI agent runs on OpenClaw and has been on WhatsApp from day one. WhatsApp is great for family-context stuff — reminders, location checks, calendar summaries. But it's not ideal for every use case. Telegram has better bot support, cleaner threading, and I wanted a second channel for different use cases. The pairing flow for Telegram is simple: Create a bot via @botfather, grab the token Add the token to OpenClaw config under channels.telegram DM the bot and approve the pairing request That part worked first try. The bot responded, pairing was approved, and I had a live Te