Lesson 869 of 2116
OpenClaw Heartbeats: Letting A Soul Think Without You
A heartbeat is what makes an OpenClaw soul autonomous — a run-loop the runtime fires on its own, so the agent can think, check, and act between your messages.
Lesson map
What this lesson covers
Learning path
The main moves in order
- 1What a heartbeat is
- 2heartbeat
- 3agent loop
- 4autonomous run
Concept cluster
Terms to connect while reading
Section 1
What a heartbeat is
Most agent frameworks are reactive — a user sends a message, the model responds, the loop ends. OpenClaw treats agents differently. A soul (OpenClaw's word for an agent instance) has a heartbeat: a run-loop the runtime fires on its own, on a schedule or in response to events, with no human prompt required. The soul wakes up, looks at its memory and tools, decides whether to act, and goes back to sleep. Then it does it again.
Why souls need heartbeats
- 1Background reflection: a soul that processes today's conversation while you sleep produces better recall tomorrow
- 2Proactive notification: 'remind me to follow up with Sam' is impossible without a wakeup that isn't tied to a user message
- 3Long-running goals: 'monitor the bug-tracker every 10 minutes and ping me when X happens' needs a loop that doesn't end with a single response
- 4Memory consolidation: turning short-term notes into durable memories takes a separate pass that no user request triggers
- 5Tool-driven workflows: an agent that watches an inbox, queue, or webhook needs to run when the world changes, not when the human asks
How a heartbeat differs from cron
A platform cron job — like Vercel's vercel.json crons — fires an HTTP route on a schedule. That's a wakeup for the platform. An OpenClaw heartbeat fires inside the agent runtime: the soul keeps its memory, its tool handles, and its current goal between beats. Cron triggers stateless functions; heartbeats keep state. You can use cron to fire a heartbeat, but a heartbeat is the agent-side concept — the part that makes the soul feel always-on.
Compare the options
| Reactive agent | Heartbeat soul |
|---|---|
| Runs only when user sends a message | Runs on schedule, on events, or both |
| State lives in chat history | State lives in soul memory between beats |
| Latency = round-trip time | Latency = time-to-next-beat (set by you) |
| Can't act without user | Can act, then notify the user about it |
| Cheap when idle | Costs tokens even with no user activity |
What a single beat looks like
- 1The runtime fires the heartbeat (timer or event)
- 2The soul loads its current memory and tool set
- 3It runs one model pass: 'given my state and the trigger, do I act?'
- 4If yes: it calls tools, updates memory, optionally sends a message
- 5If no: it logs the no-op and goes back to sleep
- 6The loop closes; the next beat is scheduled
Key terms in this lesson
The big idea: a heartbeat is the runtime tapping your soul on the shoulder. Reactive agents wait. Heartbeat souls live in the room with you and occasionally do something on their own.
End-of-lesson quiz
Check what stuck
15 questions · Score saves to your progress.
Tutor
Curious about “OpenClaw Heartbeats: Letting A Soul Think Without You”?
Ask anything about this lesson. I’ll answer using just what you’re reading — short, friendly, grounded.
Progress saved locally in this browser. Sign in to sync across devices.
Related lessons
Keep going
Creators · 9 min
OpenClaw: Souls, Heartbeats, And Skills
OpenClaw is an open-source agentic framework built around three primitives — souls (persistent personas with memory), heartbeats (autonomous loops), and skills (pluggable capabilities). Knowing those three tells you when OpenClaw is the right fit.
Creators · 9 min
What Perplexity Is: Search-Augmented LLM, Not A Chatbot
Perplexity is built around the idea that every answer should cite its sources. Treating it like ChatGPT misses the point — and the reliability gap that comes with it.
Creators · 10 min
Spaces: Building Team Knowledge Bases In Perplexity
Spaces are Perplexity's project containers — system prompts, files, and shared chat history. They turn the search engine into a research workspace.