Telegram is where you steer the agent and where results land. EasyClaw is optimized for short, high-signal messages — reminders, briefings, follow-ups, monitoring summaries — not for endless role-play threads. Think “operator console,” not “novelty chat.”
What Telegram is for
A single persistent thread with your bot that receives both your commands and proactive deliveries from automations, integrations, and scheduled runs on the managed OpenClaw runtime.
How conversations work
- You send plain-language instructions (“remind me…”, “what do I have today…”).
- The agent may call tools (calendar, RSS, HTTP on Pro) within budgets defined by your plan.
- Scheduled work fires on its own and appends to the same chat, so you see a timeline of what the system did for you.
When to use Telegram vs the dashboard
- Telegram: quick requests, habit language, reading outputs, lightweight course corrections.
- Dashboard: OAuth integrations, RSS URLs, webhook secrets, automation templates, usage — things that should be auditable and stable.
Examples that work well
- “Remind me in 45 minutes to send the invoice.”
- “What reminders are active?” / “What automations are running?”
- “Send me Daily Control every weekday at 7:15am.” — see Daily Control.
- “Summarize new items from this RSS every morning.” — pair with Monitoring.
Plans and limits
Chat turns consume the same fair-use envelope as other runs. Advanced tools (browser-heavy work, HTTP fetch, inbound webhooks) may be Pro-only. Read Starter vs Pro instead of guessing from chat alone.
Common mistakes
- Pasting API keys or webhook URLs into Telegram — use dashboard fields.
- Expecting the bot to silently access systems you never connected — scope is always explicit.
- Mixing languages is fine, but keep instructions one intent per message for more reliable handling.
Related
Next step: set up integrations in the dashboard, then return here to phrase habits that use that data.