[BUG] Switching TUI renderer (/tui) silently discards a just-performed /rewind

Open 💬 0 comments Opened Jul 4, 2026 by jayenashar

Environment

  • Claude Code v2.1.201, CLI
  • Linux (Debian, kernel 6.1), running inside tmux (TERM=tmux-256color)
  • "tui": "fullscreen" in ~/.claude/settings.json

Summary

Switching the TUI renderer with /tui after a /rewind reverts the session to its pre-rewind state, as if the rewind never happened. The user gets no warning; the rewind is silently lost.

Context: with the fullscreen renderer the /rewind picker shows only ~2 entries (#74097), so the natural workaround is to switch to the classic renderer to rewind. This bug makes that workaround fail.

Steps to reproduce

  1. Start a session with the fullscreen renderer and have a conversation with several prompts.
  2. /tui default
  3. /rewind, select an earlier checkpoint, confirm. The conversation is rewound.
  4. /tui fullscreen

Actual: the session is back at the pre-rewind end of the conversation.

Expected: the rewind survives a renderer switch.

It looks like the /tui switch re-hydrates the session from the transcript on disk, which still contains the full history, so the in-memory rewind state is thrown away.

Notes

Originally this issue also described the picker-height difference; that part is tracked in #74097 (filed earlier, missed by my duplicate search due to search-index lag). This issue now covers only the state loss on renderer switch.

View original on GitHub ↗