--- title: "Build a Personal AI Assistant on Telegram in Under 5 Minutes" description: "Set up a private, always-on AI assistant on Telegram without BotFather, Docker, or API keys. AgentRoost provisions the bot for you — AI credits included." canonical: https://agentroost.app/en/blog/personal-ai-assistant-telegram-5-minutes date: 2026-05-31T20:00:00Z --- [Canonical URL](https://agentroost.app/en/blog/personal-ai-assistant-telegram-5-minutes) # Build a Personal AI Assistant on Telegram in Under 5 Minutes Most guides for a Telegram AI bot start the same way: "First, open BotFather and send `/newbot`…" and then they're 15 steps deep before a single line of Python has run. By the time you've rented a VPS, set up SSL, sourced an OpenAI key, kept the token out of Git, and wired a webhook, an hour has evaporated — and you still have to maintain the thing. There's a faster path. This walkthrough skips every one of those steps. --- ## What You're Actually Building A private, **owner-locked** Telegram bot that: - Replies to your messages with a capable LLM (choose from 350+ models) - Persists conversation context across days — it remembers what you told it yesterday - Runs 24/7 on dedicated hardware; you don't keep a laptop open - Has no other user — it responds to you and no one else The use cases are immediate: a personal research assistant, a daily briefing bot, a writing helper, a second brain for quick lookups when you're on your phone. --- ## The Hard Way (What Most People Attempt) To build this yourself, you typically need: 1. A Telegram bot token from BotFather 2. A VPS or a serverless function host (cold starts = broken conversations) 3. An API key from OpenAI, Anthropic, or whoever — entered in plain text somewhere 4. A process manager (systemd, PM2, Docker) so it doesn't die overnight 5. HTTPS for webhook delivery — meaning a domain + TLS cert, or Cloudflare tunnels 6. Conversation state storage (Redis, SQLite, a Postgres instance) That's six moving parts for what should be a simple utility. And it's yours to maintain when any one of them drifts. --- ## The Fast Way: OpenClaw on AgentRoost [OpenClaw](/en/agents/openclaw) is a persistent AI assistant framework — your conversation and file state live on the same always-on container as the bot. AgentRoost auto-provisions the Telegram bot for you at launch; you never touch BotFather. **What's included, with no extra setup:** - Auto-provisioned, owner-locked Telegram bot (only your Telegram account can talk to it) - LLM/AI credits bundled into the subscription price — no API key required, AI works on day one - Persistent memory: context survives restarts, container updates, and days of silence - Public HTTPS endpoint managed for you; no SSL cert to renew ### Step-by-Step: From Zero to Chatting in ~2 Minutes **1. Create your account** Go to [agentroost.app](/en/agents) and sign up with email/password, Google, Microsoft, or Discord. **2. Pick OpenClaw** From the dashboard, choose **OpenClaw** as your framework. Give the instance a name — something like `my-assistant` or `research-bot`. **3. Launch** Hit the launch button. AgentRoost provisions a container, generates your private Telegram bot, and links it to your account. The whole thing takes about two minutes. **4. /start your bot** You'll see a button to open the **AgentRoost manager bot** — a lightweight bot that lists all your running agents. Tap your OpenClaw instance, press **Start**, and your private bot pops up in Telegram. Send it a message. It replies. That's it. > **No BotFather session. No YAML config. No API key pasted into an environment file.** --- ## What to Do With It Once It's Running The first message you send should orient the assistant. Because context persists, whatever you tell it now is still there tomorrow. A few opening messages that pay off quickly: - **"You are my personal research assistant. I work in [your field]. When I ask you to research something, give me a structured summary with sources."** - **"I'll send you raw notes throughout the day. Summarize them every time I say 'end of day recap'."** - **"Act as a writing editor. When I send you a draft, highlight weak sentences and suggest rewrites, but don't rewrite the whole thing."** Because the context window persists across sessions, the assistant learns your preferences over time without you repeating them on every message. --- ## OpenClaw vs. Hermes: Which Framework to Pick? Both run on Telegram, but they're aimed at slightly different needs: | | **OpenClaw** | **Hermes** | |---|---|---| | Primary use | Conversational AI assistant | Scheduled tasks + monitoring + multi-step research | | Memory model | Persistent conversation context | Context across days + task memory | | Best for | Q&A, writing help, daily use | Alerting, inbox summaries, autonomous research loops | | Setup | Name it, /start, done | Name it, /start, then configure tasks/prompts | If you want to *chat*, pick OpenClaw. If you want the assistant to *do things on a schedule* — check a feed, summarize your inbox, send you a morning briefing — look at [Hermes](/en/agents/hermes). --- ## Why AI Credits Being Included Actually Matters Every competing option — Elestio, Sliplane, Hostinger, Hermify — gives you the container but not the AI. You bring your own OpenAI or Anthropic key, and you manage that billing separately. The credit meter ticks on a second invoice you're watching. On AgentRoost the LLM calls are part of the subscription. From $19.99/mo you get the server *and* the AI budget together. For a personal assistant that handles moderate daily use, most people never think about credits at all — they just use it. If you want heavier workloads or more capable models, Plus and Pro tiers add more compute and more included credits. You can switch the model your assistant uses at any time — 350+ are available — without touching any config. --- ## How to Do This on AgentRoost (Quick Reference) 1. [Sign up](/en/agents) — takes about 30 seconds 2. Pick **OpenClaw** (or **Hermes** if you want scheduled tasks) 3. Name the instance → Launch 4. Open the manager bot → `/start` your agent 5. Send your first message No Docker. No BotFather. No separate API bill. The 14-day money-back guarantee means there's no risk in trying it. [Compare plans and pricing →](/en/pricing) --- ## Tips Once You're Up and Running - **Switch models without downtime.** From the AgentRoost dashboard you can change which LLM backs your assistant. Try a reasoning-focused model for research, a faster model for quick replies. - **File context.** OpenClaw persists file state alongside conversation state — you can drop a document into the chat and reference it in follow-up messages. - **Keep your system prompt short.** One clear paragraph of persona + instructions outperforms a 20-bullet prompt for daily-use assistants. - **Don't restart it unless you need to.** The whole point is that it's always on — treat it like a utility, not a script you run when you need it.