openclaw - 💡(How to fix) Fix [Feature]: Support disabling heartbeat via config [1 comments, 2 participants]

Setting "heartbeat": false results in a config validation error and the

• Error observed: reload-invalid-config → config restored from backup

TL;DR

The heartbeat feature can be disabled by introducing a valid "disabled" config option, such as setting "heartbeat": null or adding an explicit flag.

Guidance

• Introduce a new config option to explicitly disable the heartbeat feature, for example, by setting "heartbeat": null or using an object with an "enabled": false flag.
• Update the config schema to accept the new "disabled" config option, ensuring backward compatibility with existing configurations.
• Consider adding a string shorthand like "heartbeat": "off" for easier configuration.
• Verify the fix by testing the new config option and ensuring the Gateway does not fall back to the last-known-good config.

Example

{
  "heartbeat": null
}

or

{
  "heartbeat": {
    "enabled": false
  }
}

Notes

The proposed solution should be tested thoroughly to ensure it does not introduce any unintended side effects or errors.

Recommendation

Apply workaround by introducing a new config option, as it provides a clear and explicit way to disable the heartbeat feature.