openclaw - 💡(How to fix) Fix [Bug]: TUI session resets spontaneously — loses all context and switches agent without user action [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#59018Fetched 2026-04-08 02:29:51
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
Participants
Timeline (top)
cross-referenced ×3

The TUI session resets on its own without any user action. All conversation context is lost and the agent switches automatically to a different agent/model. The user did nothing — it happened while they were watching the screen.

Error Message

  • #59008 — NO_REPLY from models, no error shown

Root Cause

The TUI session resets on its own without any user action. All conversation context is lost and the agent switches automatically to a different agent/model. The user did nothing — it happened while they were watching the screen.

RAW_BUFFERClick to expand / collapse

Summary

The TUI session resets on its own without any user action. All conversation context is lost and the agent switches automatically to a different agent/model. The user did nothing — it happened while they were watching the screen.

Behavior

  • Session was active and responding (Arthur, kimi/k2p5)
  • Without any user input, session resets completely
  • All conversation history/context gone
  • Agent changed without permission

Why this is critical

Context loss in an AI agent session means all in-progress work, instructions, and state are destroyed. For long-running sessions with complex tasks this is catastrophic. The user should be in full control of when a session ends.

Combined damage from 2026.4.1 — full list of issues filed today

This update has destroyed an entire working day. Issues filed:

  • #57437 — UI Save wipes entire config
  • #58881 — exec.ask=off ignored, approval popups can't be disabled
  • #58885 — Sandbox auto-enabled on update, breaks all exec
  • #59003 — exec security defaults lock out operators with no escape
  • #59006 — Full day lost, zero tasks completed due to update
  • #59008 — NO_REPLY from models, no error shown
  • #59010 — Popup flood, no way to dismiss permanently
  • #59014 — TUI input vanishes silently
  • #59017 — 35+ skills broken by sandbox isolation
  • This issue — spontaneous session reset, context lost, agent switched

This is 10 separate bugs introduced by a single update. A working production setup was completely destroyed. This must not happen again — breaking changes of this magnitude need a migration guide, opt-in toggles, and a rollback path.

extent analysis

TL;DR

The most likely fix for the spontaneous TUI session reset issue is to revert or rollback the recent update (2026.4.1) that introduced this and several other critical bugs.

Guidance

  • Review the changelog and release notes for update 2026.4.1 to understand the intended changes and potential breaking points.
  • Investigate if there's an option to disable the new features or revert to the previous version's behavior, possibly through configuration settings or environment variables.
  • Consider reaching out to the development team or community forums for temporary workarounds or patches that might address the session reset issue without fully rolling back the update.
  • Evaluate the feasibility of implementing a custom solution to persist conversation context and state externally, to mitigate the impact of session resets.

Example

No specific code example can be provided without more details on the implementation, but exploring session management and state persistence mechanisms in the TUI and agent codebases might offer insights.

Notes

The introduction of multiple critical bugs with a single update suggests a need for more rigorous testing and a rollback strategy. Without specific technical details on the TUI and agent implementation, providing a precise fix is challenging.

Recommendation

Apply workaround: Given the critical nature of the issues introduced by update 2026.4.1, rolling back to a previous version or applying a workaround that mitigates the session reset issue seems prudent until a stable fix is available.

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