The dashboard is where you configure what EasyClaw is allowed to know and how often it should work without you typing a message. Telegram remains the surface you read; the dashboard is thecontrol plane for integrations, templates, budgets, and audit trails.
What the dashboard is for
Long-lived settings that should not live in a chat transcript: models, timezone, automations, OAuth tokens, webhook secrets, and usage. Everything ultimately feeds the same managed OpenClaw runtime that powers Telegram delivery.
How the main areas fit together
- Home / overview — shortcuts into the tasks you do most (connect Telegram, open automations, see status).
- Config / model — default model, timeouts, toggles that shape how aggressive or patient the agent is.
- Automations — scheduled jobs and templates (Daily Control, RSS pulls, HTTP fetch or inbound webhook when Pro). This is the heart of background execution.
- Memory — durable facts the agent can reuse across runs (preferences, standing instructions) when enabled.
- Usage / runs — how much you have consumed; authoritative when docs disagree with memory.
When to open the dashboard
- First day: connect Telegram, set timezone, pick a model.
- Weekly: tweak automations, add RSS feeds, review failures.
- Before upgrading: confirm which Pro features you actually need — Starter vs Pro.
Examples
- Create a morning Daily Control automation after Google Calendar is linked — see Daily Control.
- Add an RSS feed for a changelog and schedule a digest — see Monitoring.
- Generate an inbound webhook URL for CI notifications — Inbound webhooks (Pro).
Plans and limits
Some tiles or actions only appear for Pro (HTTP fetch, inbound webhooks, certain monitoring builders). If a button is disabled or an error references your plan, read Starter vs Pro and checkout.
Common mistakes
- Configuring automations but forgetting to link Telegram — runs succeed technically with nowhere to deliver.
- Leaving timezone unset and wondering why 7am automations fire “late.”
- Treating Usage as cosmetic — it is the first place to look when Telegram goes quiet.
Related
Next step: connect your first integration under Automations, then validate delivery using Telegram patterns.