Why your AI agent needs a heartbeat

Here's a question: if your AI agent only does something when you ask it to, is it really an agent? Or is it just a very fast search bar?

Most OpenClaw setups are reactive. You send a message. It responds. You close the chat. It goes dormant. Nothing happens until you show up again.

A heartbeat changes that.

What a heartbeat actually is

A heartbeat is a scheduled poll — a regular check-in that runs every 30–60 minutes even when you're not actively chatting. During each heartbeat, your agent runs through a checklist: is there anything that needs attention? Any emails to flag? Any deadlines approaching? Any open tasks that have been stuck too long?

If yes — it tells you. If no — it stays quiet. Silence is the default. The goal is signal, not noise.

What a good heartbeat checks

Inbox monitoring. Any new emails from clients, leads, or important contacts? If a reply came in from an outreach email sent yesterday, you want to know now — not when you happen to check your email three hours later.

Calendar alerts. Any events in the next 2 hours? If there's a meeting in 90 minutes and you haven't looked at the agenda yet, your agent should surface that now.

Project health. Any active projects that haven't had an update in 24+ hours? Any approaching deadlines? A good agent flags drift before it becomes a crisis.

Open loops. Is anyone waiting on a reply from you for more than a few hours? Did you say you'd do something yesterday and it hasn't been done?

Lead generation. If you've set up autonomous prospecting, the heartbeat is when new leads get surfaced for your review — complete with drafted outreach emails, ready to approve or discard.

The HEARTBEAT.md file

In a well-configured OpenClaw setup, the heartbeat is driven by a file called HEARTBEAT.md in your workspace. It contains the checklist your agent runs through on every poll. You control what gets checked. The agent controls when and how.

# HEARTBEAT.md

## Every cycle
- Check inbox for urgent emails
- Scan calendar for events in next 2h
- Review active projects for blockers
- Surface any leads ready for review

## Morning only (after 7am)
- Send daily brief

Simple, readable, editable. If your priorities change, you update the file and the agent adapts immediately.

What heartbeats are not

A heartbeat isn't a nagging system. Your agent shouldn't message you every 30 minutes saying "I checked your inbox and there's nothing new." Silence is fine. The heartbeat runs — and if there's nothing to report, it logs that it ran and stops there.

The value is in the exceptions. When something matters, you hear about it immediately. When nothing matters, you hear nothing. That's the design.

Getting started

To add a heartbeat to your OpenClaw setup, you need two things: a HEARTBEAT.md file defining the checklist, and a cron job that triggers the agent every 30 minutes. Both can be set up in about 10 minutes if you know what you're doing.

Or you can skip the setup entirely — every AgentStore persona comes with HEARTBEAT.md pre-configured and ready to run.