Telegram is the channel ShipClaw was built around. Get a bot token from @BotFather, paste it into the dashboard, and your OpenClaw agent is live in a chat — typing, browsing the web with the stealth engine, and answering as the personality you picked.
ShipClaw calls Telegram's setWebhook with your agent's per-bot path. You don't run ngrok, you don't expose a port, you don't write a handler.
First chat to message the bot is the owner. Strangers who get a stale invite link won't get a reply. No 'who is this guy' moment.
Each agent in your account gets its own Telegram account binding and webhook path. Build a fleet of bots without forking ShipClaw.
/telegram-webhook/{agentId} paths so multiple bots on one account don't collide. You can move a token between agents without webhook surgery.
Six-phase lock flow across the in-memory layer, pool-settings.json, and openclaw.json. Survives process respawn and node migration.
10-second debounce on agent edits prevents kill-respawn during rapid config changes. Your bot stays online while you tinker.
Telegram agents idle out at 60 minutes (vs. 15 for non-Telegram) so an active conversation never restarts mid-thread.
Ask the bot to fetch a page, search a database, or fill a form — it actually loads the live web through the bundled stealth engine.
Open Telegram, message @BotFather, send /newbot, follow the prompts, and BotFather replies with a token like 123456789:ABC-DEF... You paste that into ShipClaw and we register the webhook with Telegram automatically. Don't post the token publicly — anyone with it can hijack the bot until you rotate it.
When a fresh Telegram bot is connected, the first chat that messages it is recorded as the owner and the bot stops responding to anyone else. This stops a leaked invite link from being co-opted by a stranger before you've even tested it. The lock is stored across the in-memory layer, pool-settings, and openclaw.json so it survives respawn.
Yes. Each agent gets its own Telegram account binding (keyed by agentId, not 'default'), its own webhook path under /telegram-webhook/{agentId}, and its own per-agent webhook URL. They share a webhook port but are routed by path so they don't collide.
First message after idle pays a cold-start cost while the OpenClaw process spawns (a few seconds). Subsequent messages are bound by Anthropic latency for the model you picked — Haiku is fastest, Sonnet is balanced, Opus trades latency for reasoning depth. Idle timeout for Telegram-bound agents is 1 hour, so within an active conversation there's no respawn.
Want a different channel? Discord hosting · WhatsApp hosting.
Every instance comes with a stealth browser engine, CAPTCHA bypass, and autonomous web actions built in. Your agent doesn't just talk — it browses, searches, and gets things done.
Get StartedNo credit card required. No servers to manage. Ever.