Skip to content

Keep periodic OpenClaw heartbeats disabled across releases - #3215

Open
xeophon wants to merge 1 commit into
codex/3205-openclaw-sanitizerfrom
codex/3205-openclaw-heartbeat
Open

xeophon wants to merge 1 commit into
codex/3205-openclaw-sanitizerfrom
codex/3205-openclaw-heartbeat

Conversation

@xeophon

@xeophon xeophon commented Nov 19, 2026 •

Copy link
Copy Markdown
Member

Keep recurring heartbeat turns disabled on OpenClaw 2026.10.9 and omit its retired setting on 2026.11.5. The installer checks the installed gateway’s configuration schema once and caches whether the setting is supported. The generated configuration sets the heartbeat interval to zero only when supported. Explicitly scheduled automation jobs retain their existing configuration. Both release binaries validated their generated configs. 2026.10.9 heartbeat scheduling · 2026.11.5 migration

Local unit suite on this commit reported 299 passed, 19 skipped. Full-stack CI before review fixes

Layer 8 of 13. Builds on #3214. Stack index

Note

Keep periodic OpenClaw heartbeats disabled across releases

  • The setup script probes the installed OpenClaw schema for an agents-defaults heartbeat property and caches the result (1/0) in a marker file, written via temp file and rename.
  • OpenClawHarness config generation reads the marker and includes the zero-minute heartbeat setting only when the schema supports it; older OpenClaw versions get no heartbeat setting instead of a config that fails to parse.

Macroscope summarized 2752ebf.


Note

Low Risk
Targeted compatibility shim for OpenClaw gateway config schema differences; no auth, data, or security surface changes.

Overview
OpenClaw harness config now adapts to whether the installed gateway still accepts agents.defaults.heartbeat.

During install/setup, the harness runs config schema once and caches a has-heartbeat-setting flag (1/0) by checking if agents.defaults.properties includes heartbeat. When building the per-task config in prepare_acp, heartbeat: { every: "0m" } is no longer always written; it is added only when that cached flag is 1, so newer OpenClaw builds that reject the setting (e.g. 2026.11.5) start cleanly while older gateways can still disable the default heartbeat schedule.

Reviewed by Cursor Bugbot for commit 2752ebf. Bugbot is set up for automated code reviews on this repo. Configure here.

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 13065f5. Configure here.

@macroscopeapp

macroscopeapp Bot commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

Approvability

Verdict: Approved at 2752ebf

Macroscope's review found this PR approvable — OpenClaw configuration now adapts to whether the installed release supports the heartbeat setting, preserving disabled periodic heartbeats without emitting a retired option. The change is confined to version-scoped setup and task configuration, with no material expansion of access or data exposure.

You can add or adjust custom eligibility rules. Learn more.

@xeophon
xeophon force-pushed the codex/3205-openclaw-sanitizer branch from a709b3d to 3f656bf Compare November 19, 2026 01:30
@xeophon
xeophon force-pushed the codex/3205-openclaw-heartbeat branch from 13065f5 to 2752ebf Compare November 19, 2026 01:30
@xeophon xeophon changed the title Omit the retired OpenClaw heartbeat setting Keep periodic OpenClaw heartbeats disabled across releases Nov 19, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant