How to Disable OpenClaw Heartbeats While You Test Your Setup

How to Disable OpenClaw Heartbeats While You Test Your Setup

If OpenClaw heartbeats are firing too often while you are still testing, it can make the setup feel noisy and harder to trust. A simple fix is to disable heartbeats until everything is working the way you want.

• Last updated: April 2026

Disable OpenClaw heartbeats while testing

Why Disable OpenClaw Heartbeats?

By default, OpenClaw heartbeats can run on a schedule and check in regularly. However, while you are still tuning prompts, automation, or memory behavior, those background runs can create extra noise. Therefore, disabling heartbeats is a smart temporary step until you trust the setup.

The Setting to Change

Add this setting to your live OpenClaw config:

{
  "agents": {
    "defaults": {
      "heartbeat": {
        "every": "0m"
      }
    }
  }
}

Which File to Edit

The live config file is:

/home/user/.openclaw/openclaw.json

Video Walkthrough

If you want a quick visual example, watch the short screencast below.

What This Setting Does

Setting agents.defaults.heartbeat.every to "0m" disables heartbeats. In other words, OpenClaw stops doing those scheduled heartbeat runs until you turn them back on again.

When This Is a Good Idea

  • You are still testing your AI agent setup
  • You do not want random nudges or automated check-ins yet
  • You want fewer background API calls
  • You are still adjusting memory, prompts, or session behavior

When to Re-enable Heartbeats

Once your OpenClaw setup feels stable, heartbeats can become useful again. For example, they can help with reminders, inbox checks, or periodic review tasks. Until then, keeping them off is often the cleaner move.

Related OpenClaw Pages

Finally, disabling heartbeats is not a forever setting. It is simply a good way to reduce noise while you are still building trust in your OpenClaw setup.