openclaw - 💡(How to fix) Fix `/new` does not clear persisted model override in channel-bound sessions

Problem

When using a channel-bound session (e.g., Feishu DM), calling /model <provider/model> persists a model override for that session. After calling /new, the conversation history is reset, but the model override remains active.

This means the new session continues using the old model instead of the configured agents.defaults.model.primary.

Reproduction Steps

1. In a Feishu DM (persistent session key), manually switch model: /model deepseek/deepseek-v4-pro
2. Start a new session: /new
3. Check status: /status still shows deepseek/deepseek-v4-pro, not the configured default bailian/qwen3.6-plus

Root Cause

Feishu DM sessions use a fixed session key (agent:main:feishu:direct:ou_xxx). /new resets the transcript but does not clear the persisted model override from the previous conversation.

Impact

Users with fallback chains configured are especially affected:

• They manually switch to a fallback model (e.g., deepseek/deepseek-v4-pro)
• After /new, they expect to return to the primary model
• Instead, the fallback persists silently

Suggested Solutions

Option A (recommended): /new should automatically clear any persisted model override and restore the session to agents.defaults.model.primary.

Option B: Add a config option:

{
  "sessions": {
    "resetModelOnNew": true
  }
}

Option C: /model default should resolve to the actual configured agents.defaults.model.primary (bailian/qwen3.6-plus), not to a literal bailian/default model name. Currently it fails with: "Model bailian/default is not allowed".

Environment

• OpenClaw version: 2026.5.7
• Channel: Feishu DM
• Config: agents.defaults.model.primary: bailian/qwen3.6-plus with fallbacks to minimax/MiniMax-M2.7 and deepseek/deepseek-v4-pro

Workaround

Currently requires explicit: /new bailian/qwen3.6-plus every time, or /model bailian/qwen3.6-plus after /new.