What is OpenClaw on Telegram?
A Hacker News comment from a few months ago stuck with me. Someone said they tried five different AI agent platforms and the only one they kept using was the one connected to Telegram. Not because it was the smartest or the cheapest, but because it was always right there in their phone, sitting between their group chats and their news channels.
OpenClaw on Telegram is exactly that. Your AI agent, accessible as a Telegram bot, doing real work on a real computer. You message it the same way you message a friend.
Why Telegram and not a web app
OpenClaw supports multiple messaging channels: Telegram, WhatsApp, Discord, Slack. But Telegram is what most users pick, and for good reasons.
Telegram syncs across every device you own. You can start a task from your phone on the bus and check the result from your desktop at work. Messages have no length limit, so the agent can send back full reports without truncation. File sharing works natively, which means you can send a spreadsheet to your agent and get a cleaned version back, all inside the same conversation thread.
And there is no app to install beyond Telegram itself, which most people already have. Your agent is just another contact in your chat list. No new interface to learn, no dashboard to bookmark, no password to remember.
How it works technically
The connection between OpenClaw and Telegram goes through the Telegram Bot API. You create a bot via BotFather (Telegram’s built-in bot creation tool), get a token, and configure OpenClaw to use that token. Once connected, your messages route from Telegram to OpenClaw’s gateway, which passes them to the AI model, which decides what to do, and the results flow back through the same path.
The architecture guide covers this in more detail, but the short version is: your Telegram message triggers the agent to act on a real computer with a browser and terminal, and the response comes back as a regular Telegram message.
If you are self-hosting, you need to set up HTTPS webhooks for Telegram to deliver messages to your server. The Ubuntu install guide and Mac guide both cover this. It is not difficult, but it does require a domain name and a reverse proxy.
What it looks like in practice
You open Telegram, tap your OpenClaw bot, and type something like: “Find the cheapest round-trip flights from SFO to Tokyo in April and put the top 5 options in a table.”
The agent opens a browser, searches flight comparison sites, collects pricing data, and sends you back a formatted table. Maybe it takes two minutes. You get a notification on your phone like any other Telegram message.
People run all kinds of tasks this way. Research, web scraping, file processing, code generation, scheduled monitoring. And the full list of use cases gives more examples, but the pattern is always the same: send a message, get a result.
Managed vs. self-hosted Telegram setup
Self-hosting means creating your own Telegram bot, configuring the token, setting up webhooks, and maintaining the server. It works, but there are a few moving pieces that need to stay running. So the question is really about how much setup you want to take on.
OpenClaw Cloud was built with Telegram as the default channel. There is no BotFather step, no webhook configuration, no server to maintain. You open Telegram, connect your API key, and start chatting. The entire setup takes about three minutes, and because the infrastructure is managed, the agent stays online without you thinking about it.
Both approaches give you the same core experience: an AI agent in your Telegram chat that can do real work. The difference is just who handles the plumbing. If you want to skip the server setup, the waitlist is open.