status reporting wrong model | Friends of the Crustacean 🦞🤝 | Page 1

topaz garden Apr 16, 2026, 7:30 PM

#

I noticed that openclaw status is showing this for my heartbeat:
Key │ Kind │ Age │ Model │ Tokens │
├─────────────────────────────────────────┼────────┼─────────┼────────────────────────┼────────────────────────────────┤
│ agent💓main:heartbeat │ direct │ 1m ago │ gemini-3-flash-preview │ 7.3k/16k (44%)

First the heartbeat is set to run on google/gemini-3.1-flash-lite-preview, and that is what google ai studio is showing. May be an issue with status?

I am on v2026.4.14

grave havenBOT Apr 16, 2026, 7:30 PM

#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

sterile matrixBOT Apr 16, 2026, 7:30 PM

#

topaz garden Apr 16, 2026, 7:35 PM

#

@charred smelt where did you go?

charred smeltBOT Apr 16, 2026, 7:38 PM

#

Was digging through the source 😅

Yeah, this looks like a status/reporting mismatch, not the heartbeat necessarily using the wrong model.

What I found:

heartbeat runs do accept a per-run heartbeat.model override
for isolated heartbeat sessions like ...:heartbeat, openclaw status prefers a persisted session override if one exists
the heartbeat override is passed into the run, but it does not appear to be surfaced as a stored session /model override for status rendering
so status can fall back to the session/default model or last recorded runtime model instead of the configured heartbeat model

So your case is consistent with:

configured heartbeat model: google/gemini-3.1-flash-lite-preview
actual provider usage: flash-lite
openclaw status row showing gemini-3-flash-preview anyway

I’d treat that as a status bug on v2026.4.14.

#

Docs:

If you want, paste openclaw status --all and I can sanity-check whether it’s pure display drift or whether a fallback also happened. If this is enough to confirm it, please file it here: https://github.com/openclaw/openclaw/issues

topaz garden Apr 16, 2026, 7:42 PM

#

OpenClaw status --all

Overview
┌─────────────────┬────────────────────────────────────────────────────────────────────────────────────────────────────┐
│ Item │ Value │
├─────────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ Version │ 2026.4.14 │
│ OS │ linux 6.12.75+rpt-rpi-2712 (arm64) │
│ Node │ 22.22.2 │
│ Config │ ~/.openclaw/openclaw.json │
│ Dashboard │ http://127.0.0.1:18789/ │
│ Tailscale │ off │
│ Channel │ stable (default) │
│ Update │ pnpm · up to date · npm latest 2026.4.14 │
│ Gateway │ local · ws://127.0.0.1:18789 (local loopback) · reachable 62ms · auth token · rpi5 (10.0.4.22) │
│ │ app 2026.4.14 linux 6.12.75+rpt-rpi-2712 │
│ Security │ Run: openclaw security audit --deep │
│ Gateway self │ unknown │
│ Gateway service │ systemd installed · enabled · running (pid 195747, state active) │
│ Node service │ systemd not installed │
│ Agents │ 2 total · 0 bootstrapping · 0 active · 26 sessions │
│ Secrets │ none │
└─────────────────┴────────────────────────────────────────────────────────────────────────────────────────────────────┘

Channels
┌──────────┬─────────┬────────┬────────────────────────────────────────────────────────────────────────────────────────┐
│ Channel │ Enabled │ State │ Detail │
├──────────┼─────────┼────────┼────────────────────────────────────────────────────────────────────────────────────────┤

#

│ Discord │ ON │ OK │ token config (sha256:04ed34b3 · len 72) · accounts 1/1 │
│ WhatsApp │ ON │ OK │ linked · +15016665470 · auth 3m ago · accounts 1 │
└──────────┴─────────┴────────┴────────────────────────────────────────────────────────────────────────────────────────┘

Discord accounts
┌──────────┬──────────┬────────────────────────────────────────────────────────────────────────────────────────────────┐
│ Account │ Status │ Notes │
├──────────┼──────────┼────────────────────────────────────────────────────────────────────────────────────────────────┤
│ default │ OK │ token:config │
└──────────┴──────────┴────────────────────────────────────────────────────────────────────────────────────────────────┘

WhatsApp accounts
┌──────────┬──────────┬────────────────────────────────────────────────────────────────────────────────────────────────┐
│ Account │ Status │ Notes │
├──────────┼──────────┼────────────────────────────────────────────────────────────────────────────────────────────────┤
│ default │ OK │ dm:pairing · allow:+15016123831 │
└──────────┴──────────┴────────────────────────────────────────────────────────────────────────────────────────────────┘

Agents
┌────────────┬────────────────┬──────────┬──────────┬──────────────────────────────────────────────────────────────────┐
│ Agent │ Bootstrap file │ Sessions │ Active │ Store │
├────────────┼────────────────┼──────────┼──────────┼──────────────────────────────────────────────────────────────────┤
│ main │ ABSENT │ 25 │ 2h ago │ ~/.openclaw/agents/main/sessions/sessions.json │
│ heartbeat │ ABSENT │ 1 │ 16m ago │ ~/.openclaw/agents/heartbeat/sessions/sessions.json │
└────────────┴────────────────┴──────────┴──────────┴──────────────────────────────────────────────────────────────────┘

Diagnosis (read-only)

Gateway connection details:
Gateway target: ws://127.0.0.1:18789
Source: local loopback
Config: /home/akessel56/.openclaw/openclaw.json
Bind: loopback

✓ Config: /home/akessel56/.openclaw/openclaw.json
✓ Secret diagnostics (0)
✓ Restart sentinel: none
! Port 18789
Port 18789 is already in use.

pid 195747 akessel56: openclaw-gateway (127.0.0.1:18789)
Gateway already running locally. Stop it (openclaw gateway stop) or use a different port.
! Tailscale: off · unknown
✓ Skills: 14 eligible · 0 missing · /home/akessel56/.openclaw/workspace
✓ Plugin compatibility (none)
✓ Channel issues (none)

charred smeltBOT Apr 16, 2026, 7:42 PM

#

Thanks, that paste is just the Overview block, so the heartbeat session row itself is missing.

Still, nothing there changes my read. I’m still leaning status bug, specifically for the isolated ...:heartbeat session display.

If you want a tighter confirmation, paste the Sessions section from openclaw status --all, especially the row for agent💓main:heartbeat.

If that row still shows gemini-3-flash-preview while AI Studio shows google/gemini-3.1-flash-lite-preview, I’d call it a pretty solid bug report.

#

Yep, this makes me more confident it’s a status/display issue.

Two useful clues from that paste:

status --all sees two agents, main and heartbeat
the only new warning is Port 18789 is already in use, which is just status noticing your gateway is already running, not related to the model mismatch

The agent split is interesting, because it makes it even more likely status is falling back to the agent/session identity for the heartbeat store, instead of showing the per-run heartbeat.model override.

So the picture now looks like:

actual heartbeat run: google/gemini-3.1-flash-lite-preview
provider side confirms that
openclaw status row is reporting the wrong model label for the heartbeat session/store

At this point I’d call it a bug in status reporting on 2026.4.14.

If you file it, I’d include exactly these points plus the screenshot/snippet. Issue link: https://github.com/openclaw/openclaw/issues

#status reporting wrong model