Summary

The heartbeat.model config field is documented to allow per-heartbeat model overrides, but the setting is still ignored at runtime in version 2026.2.19-2. Heartbeats always use the main session's default model instead of the configured heartbeat model.

Environment

• OpenClaw version: 2026.2.19-2
• OS: Linux 6.17.0-14-generic (x64)
• Node: v22.22.0

Configuration

{
  "agents": {
    "defaults": {
      "model": {
        "primary": "minimax-portal/MiniMax-M2.5"
      },
      "heartbeat": {
        "every": "30m",
        "model": "gemini-2.5-flash",
        "target": "telegram",
        "to": "7964555583"
      }
    }
  }
}

Expected Behavior

Heartbeats should run using gemini-2.5-flash (using GOOGLE_API_KEY).

Actual Behavior

Heartbeats continue to use the main session's default model (minimax-portal/MiniMax-M2.5).

Evidence

Logs show heartbeat started but uses wrong model:

• Config shows: heartbeat.model = "gemini-2.5-flash"
• Runtime shows: agent model = minimax-portal/MiniMax-M2.5

Previous Issues

This appears to be a regression. The following issues were reported and supposedly fixed:

• [Bug]: Different model not being used for heartbeat #14279 - Fixed 2026-02-13
• Heartbeat ignores heartbeat.model when session has modelOverride #13009 - Fixed 2026-02-13
• [Bug]: Heartbeat Model Override Not Working in OpenClaw 2026.2.3-1 #9556 - Fixed 2026-02-13

Impact

Cannot use different models for heartbeats as documented. Forces use of primary model for all heartbeat runs.