EasyClaw is built around Telegram as the front door and background execution as the default. You are not supposed to “keep the AI open” — the agent is meant to run loops, react to signals, and deliver concise updates when there is something worth your attention. The engine is a managed OpenClaw runtime: isolation per agent, budgets per run, no self-hosting burden.
What the system is
A coordinated stack of (1) your instructions in chat, (2) dashboard automations on a schedule, (3) integrations that inject facts before the model answers, and (4) delivery back to Telegram when output is ready.
How execution flows
- Trigger — you message the bot, a cron fires, a feed updates, or a webhook hits (where enabled).
- Context assembly — calendar rows, RSS items, HTTP payloads, or memory snippets are attached with clear headers so the model does not hallucinate sources.
- Run — OpenClaw executes with tool and time budgets; high-risk or out-of-policy work is blocked.
- Delivery — results land in Telegram (and are logged for usage in the dashboard).
The three loops (product core)
- Daily Control — orientation: meetings, focus, what is pending. Guide: Daily Control.
- Follow-ups — persistence: bring back threads with context when follow-up is due. Guide: Follow-ups.
- Monitoring — signal: watch feeds or (on Pro) richer web-style checks; notify when it matters. Guide: Monitoring.
When EasyClaw shines
- You want recurring briefings and nudges, not one-off chats.
- You prefer Telegram because it is already where you read time-sensitive things.
- You want integrations you turn on deliberately instead of silent broad access.
Examples
- Morning Daily Control + afternoon follow-up on an unanswered email thread.
- RSS from a vendor changelog summarized twice a week in Telegram.
- Inbound deploy hook (Pro) posting a one-line status to the same chat you use for reminders — see Inbound webhooks.
Plans and limits
Every run has a budget (tools, duration, and plan-specific gates). Starter emphasizes Calendar, RSS, and Telegram-native patterns; Pro adds HTTP fetch, inbound webhooks, and richer monitoring where the product exposes them. Details: Starter vs Pro.
Common misunderstandings
- “It should silently read my whole company stack.” EasyClaw is scoped to what you connect.
- “Chat replaces the dashboard.” Some capabilities are intentionally dashboard-first for auditability.
Related
Next step: if the loops resonate, go to Get started; if you need expectations reset first, read What EasyClaw is not.