openclaw - 💡(How to fix) Fix UI: /status fallback display truncates intermediate models — show full cascade chain [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#61452Fetched 2026-04-08 02:58:25
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Participants

Code Example

Fallback: openrouter/qwen/qwen3.6-plus:free (format (+1 more attempts))
RAW_BUFFERClick to expand / collapse

Problem

When running /status (session_status), the fallback line only shows the last fallback model + a count like (format +1 more attempts). This makes it impossible to verify the intended fallback chain at a glance.

Example: With a cascade of Opus → Sonnet → GLM → Qwen, the status shows:

Fallback: openrouter/qwen/qwen3.6-plus:free (format (+1 more attempts))

The GLM model (zai/glm-5.1) is completely invisible — buried inside +1 more attempts.

Impact

Users cannot easily verify that their configured fallback chain is correct. This causes confusion (especially when debugging why a session ended up on a specific model).

Feature Request

Show the full fallback chain in the status display. Options:

  1. List all: Fallback chain: glm → qwen
  2. Inline detail: Fallback: qwen (via glm, +1 more)
  3. Expandable: keep the compact format but add a --chain flag or tap-to-expand in mobile UI

This would improve debuggability and user confidence in the fallback configuration.

Affected: session_status output / /status command

extent analysis

TL;DR

Displaying the full fallback chain in the status display, such as listing all models or providing an expandable format, would improve debuggability and user confidence.

Guidance

  • Consider modifying the session_status output to include the full fallback chain, either by listing all models or providing an inline detail of the chain.
  • Evaluate the three proposed options for displaying the fallback chain: listing all models, providing inline details, or using an expandable format.
  • Assess the impact of each option on the user interface and debugging experience.
  • Determine the technical feasibility of implementing each option, considering factors such as display space and user interaction.

Example

No code snippet is provided as the issue does not contain sufficient technical details to generate a specific example.

Notes

The solution will depend on the specific requirements and constraints of the system, including the user interface and debugging needs. The proposed options may have varying levels of complexity and feasibility.

Recommendation

Apply a workaround by modifying the session_status output to display the full fallback chain, such as listing all models or providing an inline detail of the chain, to improve debuggability and user confidence. This approach addresses the immediate need for better fallback chain visibility without requiring a full system overhaul.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING