Models page auto-populates all non-primary models into fallbacks on every save

[lizheng31]

Describe the bug

ClawPanel automatically rewrites agents.defaults.model.fallbacks to include all non-primary models whenever the models config is saved.

This makes it impossible to keep a short/manual fallback list.

As more models are added, the fallback chain becomes very long, which can cause frequent stalls / hangs during failover attempts.

---

What I expected

I expect one of these behaviors:

1. fallbacks should be user-editable and preserved as-is
2. or ClawPanel should only initialize fallbacks once when empty
3. but it should not overwrite the user's fallback list on every save

---

What actually happens

Whenever I add/edit/delete models or change the primary model, ClawPanel saves config and rewrites:

• agents.defaults.model.fallbacks
• agents.defaults.models

So the result becomes:

• primary = selected primary model
• fallbacks = all other configured models

This creates a very long fallback list automatically.

---

Source evidence

In src/pages/models.js:

function applyDefaultModel(state) {
  ensureValidPrimary(state)
  const primary = getCurrentPrimary(state.config)
  const allModels = collectAllModels(state.config)
  const fallbacks = allModels.filter(m => m.full !== primary).map(m => m.full)

  const defaults = state.config.agents.defaults
  defaults.model.primary = primary
  defaults.model.fallbacks = fallbacks

  const modelsMap = {}
  modelsMap[primary] = {}
  for (const fb of fallbacks) modelsMap[fb] = {}
  defaults.models = modelsMap
}

And this is invoked before save in auto-save flow.

So the current behavior is not accidental — it is hardcoded.

---

Why this is a problem

For users with many configured models:

• fallback chains become huge
• failover becomes noisy and inefficient
• config gets rewritten against user intent
• the UI effectively does not support "minimal fallback"
• in practice this can contribute to freezes / stalls

---

Suggested fix

Possible fixes:

1. Do not overwrite defaults.model.fallbacks if it already exists
2. Add explicit UI for editing fallback list
3. Only auto-generate fallback list when the field is missing/empty
4. Do not force-rebuild agents.defaults.models on every save

At minimum, ClawPanel should respect the user's existing fallback config.

---

Environment

• Windows
• ClawPanel managing OpenClaw config
• Multiple providers/models configured
• Problem reproducible whenever models page triggers save

[2221186349]

🤖 OpenClaw Bot 已接收此任务，正在处理...

角色: triage-external | 模型: gpt-5.4

[2221186349]

🤖 OpenClaw Bot 分析完成，但未产生代码变更。可能需要更详细的描述。

[1186258278]

已修复，见 699cf1c。感谢 @lizheng31 的报告和 PR #191 提供的修复思路。

变更：�pplyDefaultModel() 不再每次保存都重写 allbacks 和 models，仅在字段为空时初始化（首次安装友好）。primary 同步逻辑不变。