openclaw - 💡(How to fix) Fix Show model name per message/task in Control UI WebChat

Summary

When using multiple models in OpenClaw (via model switching or sessions_spawn with model overrides), there is no per-message indicator showing which model handled which response. Users must check /status or read the assistant mention to identify the active model per task. Request: Add a model-name badge/tag to each assistant message in the Control UI WebChat (and TUI) so users can instantly verify which model handled each task.

Problem to solve

Current behavior: The Control UI WebChat shows the active model in the session header only. When delegating tasks to different models via sessions_spawn(model="..."), model name is not visible per-response. No way to distinguish which model produced which message in multi-model workflows. Must rely on assistant mentioning its model or checking /status.

Pain points:

1. Multi-model workflows are confusing - cant easily verify right model handled right task
2. Debugging harder - no model attribution for low quality responses
3. Cost tracking - different models have different costs
4. Session review - no quick way to see which model per message

Proposed solution

Option A: Model badge next to assistant name (Recommended) Fox [Claude Opus 4.7] Explanation and analysis here...

Option B: Inline message metadata Fox Model: Claude Opus 4.7 0.3s

Option C: Color-coded indicator per message

The Control UI already has access to model info via session state. Data is already there - just needs per-message rendering. Should degrade gracefully if model info is unavailable.

Alternatives considered

1. Manual model mention - works but clutters messages
2. /status command - cumbersome for multi-model workflows
3. Separate sessions per model - impractical for same-context delegation

Impact

• Affected users: All multi-model OpenClaw users
• Severity: Annoying to workflow-blocking
• Frequency: Every session with model switching
• Consequence: Misattribution of responses, harder debugging

Evidence/examples

No response

Additional information

No response