Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: TUI sessions bleed model config — changing model in one session affects other sessions [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#59037•Fetched 2026-04-08 02:29:32
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
fwendsfwends
Participants
fwendsfwends

Changing the model in one TUI session causes other TUI sessions to switch to the same model without user action. Sessions should be fully isolated — a model change in session A should never affect session B.

Root Cause

Changing the model in one TUI session causes other TUI sessions to switch to the same model without user action. Sessions should be fully isolated — a model change in session A should never affect session B.

RAW_BUFFERClick to expand / collapse

Summary

Changing the model in one TUI session causes other TUI sessions to switch to the same model without user action. Sessions should be fully isolated — a model change in session A should never affect session B.

Steps to reproduce

  1. Open two TUI sessions for the same agent
  2. In session A, change model to kimi
  3. Session B automatically switches to kimi without any user input

Expected behavior

Each TUI session maintains its own model selection independently. Model changes are session-scoped, not agent-scoped.

Second bug: replies appear then vanish

In the same TUI sessions, replies from the agent appear briefly on screen then disappear completely. The message is gone from history. This happens consistently and makes the TUI completely unusable — you can see the reply for a fraction of a second then it's gone.

This is separate from the input-swallow bug (#45326) — this is the reply vanishing, not the input.

Combined state after 2026.4.1

The TUI is completely unreliable:

  • Messages typed vanish (#59014)
  • Replies appear then vanish (this issue)
  • Sessions bleed model config between each other (this issue)
  • Sessions spontaneously reset (#59018)
  • Sessions connect to stale webchat sessions instead of fresh TUI sessions

A full working day has been lost. The TUI was stable and reliable before this update.

Environment

  • Version: 2026.4.1
  • Platform: macOS TUI
  • Agent: main (Arthur)

extent analysis

TL;DR

Downgrade to a previous version or wait for a patch, as the current version 2026.4.1 has multiple critical issues affecting the TUI's stability and functionality.

Guidance

  • Verify that the issues are indeed caused by version 2026.4.1 by checking if the problems persist across different agents and platforms.
  • Test previous versions to identify when the issues were introduced and if downgrading to a specific version resolves the problems.
  • Consider reporting the issues to the development team with detailed steps to reproduce, as the current state of the TUI is unusable.
  • If possible, use an alternative interface or tool until the issues are resolved, to minimize productivity loss.

Example

No code snippet is provided, as the issue is related to the overall functionality and stability of the TUI rather than a specific code snippet.

Notes

The issues described seem to be specific to version 2026.4.1, and downgrading or waiting for a patch might be the most straightforward solution. However, without more information about the development process and testing, it's difficult to provide a more detailed fix.

Recommendation

Apply workaround: Downgrade to a previous version, as the current version has multiple critical issues that make the TUI unusable. This is recommended because the issues are widespread and affect the core functionality of the TUI.

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…

FAQ

Expected behavior

Each TUI session maintains its own model selection independently. Model changes are session-scoped, not agent-scoped.

#batch processing#GPU compatibility#latency issue#model loading#dependency error

Still need to ship something?

×6

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

Back to top recommendations

TRENDING