openclaw - 💡(How to fix) Fix Status card does not show currently active model after fallback [1 participants]

• Fails with reasoning_content error → falls back to MiniMax

TL;DR

Update the /status card to display both the configured and actual models used, including any automatic fallbacks.

Guidance

• Identify the current implementation of the /status card and how it retrieves the model information to understand why it only shows the configured model.
• Modify the /status card to also display the actual model used, including any fallback models, to provide a clear distinction between the configured and running models.
• Consider adding a clear indication of when a fallback has occurred, such as "(fallback from configured)", to ensure users are aware of the change.
• Review the logic for automatic fallbacks, such as the one due to #70392, to ensure that the actual model used is correctly tracked and displayed.

Example

// Example of updated /status card content
Model: 
  - Configured: moonshot/kimi-k2.6
  - Active: MiniMax (fallback from configured)

Notes

The exact implementation details of the /status card and the model fallback logic are not provided, so the guidance is focused on the general approach to resolving the issue.

Recommendation

Apply workaround: Update the /status card to display both configured and actual models, as this will provide the necessary clarity for users to understand when a fallback has occurred, without requiring a deeper change to the underlying model selection logic.