ai assistant daily routine productivity automation heartbeat cron openclaw morning briefing

How to Build a Daily Routine with Your AI Assistant

Turn your AI assistant into a personal chief of staff. Morning briefings, workday support, evening summaries, and automated check-ins — with real HEARTBEAT.md templates and cron configs.

How to Build a Daily Routine with Your AI Assistant

TL;DR: The most valuable thing an AI assistant does isn't answer questions — it's proactively managing your day. Set up morning briefings, workday support, evening summaries, and automated check-ins. Here's how, with copy-paste templates.


Why Routine Matters

An AI assistant you only talk to when you need something is a chatbot. An AI assistant woven into your daily workflow is a personal chief of staff.

The difference is proactive vs. reactive. A reactive AI waits for you to ask. A proactive AI messages you at 7 AM with your calendar, tells you about that important email at 10 AM, and sends a daily summary at 6 PM — without being asked.

OpenClaw supports this through two mechanisms:

  • Heartbeats: periodic check-ins where the AI reviews what needs attention
  • Cron jobs: scheduled tasks that run at exact times

Together, they turn your AI from a tool you use into a system that runs your day.


The Daily Framework

🌅 Morning (7:00 AM) — The Briefing

Start every day with a message from your AI that tells you exactly what you need to know:

What it covers:

  • Weather forecast for your location
  • Today's calendar events with preparation notes
  • Important unread emails (not all — just the ones that matter)
  • Yesterday's unfinished tasks
  • Any reminders you set

Example morning briefing:

☀️ Good morning. 18°C and sunny, rain after 5 PM.

Today's schedule:

  • 9:30 — Standup (remind Jake about the API deadline)
  • 14:00 — Design review (notes from last session: they wanted more contrast on the CTA)
  • 16:30 — Dentist (Friedrichstraße 42)

Emails worth reading:

  • Client X replied about the proposal — they want to move forward but have questions about timeline
  • AWS billing alert: $47.82 this month (up from $31 last month)

From yesterday:

  • Still need to review the PR from Maria
  • You said you'd send the invoice today

This takes your AI about 10 seconds to compile and saves you 20 minutes of checking three different apps.

Cron config:

openclaw cron add "0 7 * * 1-5" "Morning briefing: check weather, calendar for today, urgent emails, and yesterday's unfinished tasks from my daily notes"

💼 Workday (9 AM–5 PM) — On-Demand Support

During work hours, your AI is your research assistant, writing partner, and rubber duck:

Common workflows:

  • "Research [topic] and give me a summary with sources"
  • "Draft a reply to this email" (forward the email to your bot)
  • "I have a meeting about X in 20 minutes — remind me what we discussed last time"
  • "Explain this error message" (paste the stack trace)
  • "Review this document for clarity" (send the file)

Pro tip: Use Telegram topics to separate work contexts. A "code" topic, a "writing" topic, and a "research" topic keep your conversations organized and contexts clean.

📬 Afternoon (2:00 PM) — Inbox Triage

A midday check-in to catch anything that came in while you were focused:

openclaw cron add "0 14 * * 1-5" "Check my email for anything new since morning. Summarize only what needs attention. If nothing urgent, just say 'Inbox clear.'"

This is intentionally lightweight. You don't want a second morning briefing — just a quick "anything I should know?" check.

🌙 Evening (6:00 PM) — Daily Summary

End the day with a wrap-up:

What it covers:

  • What you accomplished today (pulled from conversations and tasks)
  • What's still pending
  • Tomorrow's calendar preview
  • Any reminders for the morning

Example:

📋 Daily wrap-up:

Done today:

  • Reviewed and merged Maria's PR
  • Sent the invoice to Client X
  • Drafted the blog post outline

Still open:

  • Client X's timeline questions (replied but awaiting response)
  • AWS cost optimization (investigate tomorrow)

Tomorrow:

  • 10:00 — Product planning (quarterly goals discussion)
  • No other meetings — good deep work day

Remember: You said you'd call your mom this week. Maybe tomorrow evening?

openclaw cron add "0 18 * * 1-5" "Daily summary: what I did today based on our conversations, what's still pending, and tomorrow's calendar preview"

🛋️ Weekend — Lighter Routine

On weekends, dial it back:

openclaw cron add "0 9 * * 0,6" "Weekend morning: weather, any personal calendar events, and one interesting article or fact. Keep it light."

No work email checks, no task lists. Just weather, personal events, and maybe something interesting to read. Your AI should match your energy — focused during the week, relaxed on weekends.


Setting Up Heartbeats

Heartbeats are periodic check-ins where OpenClaw reads a file called HEARTBEAT.md and acts on whatever's in it. This is perfect for recurring checks that don't need exact timing.

Template HEARTBEAT.md

# HEARTBEAT.md

## Check (rotate through these)
- [ ] Email: any urgent unread messages?
- [ ] Calendar: events in next 4 hours?
- [ ] Gateway: any errors in recent logs?

## Reminders
- If it's Monday morning: remind me to send the weekly update
- If client X hasn't replied in 48h: remind me to follow up

## Rules
- Don't check email between 10 PM and 7 AM
- Don't send me weather updates on weekdays (morning briefing covers it)
- If nothing needs attention: HEARTBEAT_OK

The AI reads this every heartbeat cycle (typically every 30 minutes) and only messages you if something needs attention. Most heartbeats result in silent HEARTBEAT_OK — which is exactly what you want.

Heartbeat State Tracking

Create memory/heartbeat-state.json to prevent redundant checks:

{
  "lastChecks": {
    "email": null,
    "calendar": null,
    "weather": null
  },
  "lastNotified": {
    "morningBriefing": null,
    "eveningSummary": null
  }
}

Your AI updates this after each check, so it knows "I already checked email 20 minutes ago, no need to check again."


Cron vs. Heartbeat: Which to Use

Use Case Cron Heartbeat
Morning briefing at 7 AM sharp
Check email "every so often"
Weekly Monday reminder
Batch multiple checks together
One-shot reminder ("in 2 hours")

Cron = exact time, isolated task. Heartbeat = periodic sweep, batched checks.

Use both. Cron for the fixed schedule (briefings, summaries), heartbeats for the ongoing monitoring (email, notifications).


Building It Gradually

Don't set up everything at once. Start with one thing — the morning briefing is the highest value — and add more as you discover what's useful.

Week 1: Morning briefing only Week 2: Add evening summary Week 3: Add email monitoring via heartbeats Week 4: Add calendar reminders and afternoon check-in

By the end of the month, you'll have a routine that feels natural, and you'll wonder how you managed without it.


The Bottom Line

The best AI assistant is one you don't have to think about using. It shows up with information you need, exactly when you need it. That doesn't happen by accident — it happens through a well-designed routine.

Set up the crons. Write the HEARTBEAT.md. Let your AI earn its keep.

Don't want to manage server infrastructure? lobsterfarm provides managed OpenClaw hosting — deployment, updates, and support handled for you.

Get started with lobsterfarm → · 15 Telegram tips →

Skip the setup. Start using your AI assistant today.

lobsterfarm gives you a fully managed OpenClaw instance — one click, your own server, running 24/7.