sessions CLI shows stale model vs session_status
sessions CLI shows a stale model name for the main agent, which doesn't match the live model reported by the gateway.
Environment
OpenClaw: 2026.2.3-1
OS: macOS
Agent: main (session key agent:main:main)
Current behavior
agents.defaults.model.primary is set to openai/gpt-5.2-codex in ~/.openclaw/openclaw.json.
/status (or session_status for agent:main:main) reports:
Model: openai/gpt-5.2-codex
openclaw sessions prints a Sessions table where the same session appears as:
Model gpt-5.1
The backing session store at ~/.openclaw/agents/main/sessions/sessions.json has:
"agent:main:main" : { ..., "model": "gpt-5.1", ... }
So the CLI's Sessions view appears to be reading a cached model field from the session store that is no longer in sync with the actual model the gateway is using.
Expected behavior
When the default model for an agent is changed (e.g. via openclaw configure --section model or config patch), either:
The session store is updated to reflect the new effective model, or
The openclaw sessions CLI derives the model column from the live gateway state instead of from a stale cached snapshot.
In either case, for an active session like agent:main:main, the model shown in the Sessions table should match the model reported by /status / session_status.
Environment
OpenClaw: 2026.2.3-1
OS: macOS
Agent: main (session key agent:main:main)
Current behavior
agents.defaults.model.primary is set to openai/gpt-5.2-codex in ~/.openclaw/openclaw.json.
/status (or session_status for agent:main:main) reports:
Model: openai/gpt-5.2-codex
openclaw sessions prints a Sessions table where the same session appears as:
Model gpt-5.1
The backing session store at ~/.openclaw/agents/main/sessions/sessions.json has:
"agent:main:main" : { ..., "model": "gpt-5.1", ... }
So the CLI's Sessions view appears to be reading a cached model field from the session store that is no longer in sync with the actual model the gateway is using.
Expected behavior
When the default model for an agent is changed (e.g. via openclaw configure --section model or config patch), either:
The session store is updated to reflect the new effective model, or
The openclaw sessions CLI derives the model column from the live gateway state instead of from a stale cached snapshot.
In either case, for an active session like agent:main:main, the model shown in the Sessions table should match the model reported by /status / session_status.
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
83,815Members
Resources
Similar Threads
Was this page helpful?
