OpenClaw Heartbeat Config Builder
Visually configure your agent heartbeat settings — intervals, prompts, the new timeoutSeconds field, and named tasks — then export valid, indentation-safe YAML. Built around PRs #64491 and #64488 merged April 10, 2026.
Why Use the Heartbeat Config Builder
Built around the latest OpenClaw heartbeat fixes and features from the open-source project.
Visual Heartbeat Builder
Configure global heartbeat defaults and named tasks through an interactive form — no manual YAML editing required.
timeoutSeconds Support
Set per-heartbeat turn timeouts using the newly added timeoutSeconds field (PR #64491). Validated as a positive integer with min 1s clamping.
Indentation-Safe Output
Generates correctly indented YAML that avoids the top-level interval/prompt bleed bug fixed in PR #64488.
Named Task Support
Define multiple heartbeat tasks with individual intervals, prompts, and timeouts. Tasks override global defaults where specified.
Real-Time Validation
Catches config errors as you type — duplicate task names, invalid timeouts, interval warnings, and inheritance hints.
Prompt Templates
Choose from pre-built heartbeat prompt templates for common use cases like health checks, email monitoring, and error scanning.
Build Your Heartbeat Config
Configure global defaults, add named tasks, and get real-time validation. The generated YAML is safe from the indentation bleed bug (PR #64488) and supports the new timeoutSeconds field (PR #64491).
Global Heartbeat Defaults
Max duration for each heartbeat turn. Must be a positive integer. Runtime clamps to min 1s.
Heartbeat Tasks
Define named heartbeat tasks with individual intervals, prompts, and timeouts. Tasks override global defaults where specified.
Indentation matters (PR #64488)
A recently fixed bug caused top-level interval and prompt fields to bleed into task blocks when indentation was wrong. This builder generates correctly indented YAML so you never hit that issue.
No tasks yet. Click "Add Task" to define named heartbeat tasks with individual settings.
Without tasks, the global heartbeat defaults above are used.
Validation
Config looks good! No issues detected.
0
Errors
0
Warnings
0
Info
Live YAML Preview
agents:
defaults:
heartbeat:
interval: 5m
prompt: "Check if all connected services are responding and report any issues."
timeoutSeconds: 30Deploy OpenClaw with DeployClaw
Get the latest heartbeat config support, automatic timeout management, and multi-agent orchestration.
Frequently Asked Questions
What is the OpenClaw heartbeat?
The heartbeat is an agent feature that runs periodic tasks on a configurable interval. It's defined under agents.defaults.heartbeat in your OpenClaw config. Each heartbeat turn executes a prompt — useful for monitoring, health checks, queue watching, and other recurring tasks.
What does the new timeoutSeconds field do?
Added in PR #64491, timeoutSeconds sets the maximum duration (in seconds) for each heartbeat agent turn. Previously this field was documented but rejected by the schema validator. It must be a positive integer — zero is rejected at config-parse time, and the runtime clamps values to a minimum of 1 second.
What was the indentation bleed bug (PR #64488)?
A parsing bug in parseHeartbeatTasks caused top-level interval: or prompt: fields appearing after a task block to overwrite that task's correctly parsed values. The look-ahead loop matched field names without checking indentation depth. The fix added an indentation check so only properly nested task fields are captured. This builder generates correctly indented YAML to avoid the issue entirely.
Can I define multiple heartbeat tasks?
Yes. Under agents.defaults.heartbeat.tasks you can define an array of named tasks, each with its own interval, prompt, and timeoutSeconds. If a task omits a field, it inherits the global heartbeat default. Task names must be unique.
What interval should I use for heartbeats?
It depends on your use case. For real-time monitoring, 30 seconds to 1 minute works well. For periodic checks like email scanning, 5–15 minutes is typical. For daily summaries, 24 hours. Be mindful that very short intervals (under 10 seconds) increase API costs significantly.
Does this tool send my config anywhere?
No. The Heartbeat Config Builder runs entirely in your browser. Your configuration is never sent to any server. The generated YAML is computed locally and can be copied to your clipboard.