Saved fullscreen renderer setting (tui: "fullscreen") is not applied to new sessions on 2.1.288

Status Open
Reported on v2.1.288
Maintainer reply None cached
Activity 0 comments · opened Oct 3, 2026

Environment

  • Claude Code 2.1.288, macOS (Apple Silicon), tested in iTerm2 and inside tmux

Steps to reproduce

  1. In any interactive session run /tui fullscreen. It prints:

> Saved. Background sessions always use the fullscreen renderer while attached; the fullscreen renderer will apply to sessions started directly with claude.

and ~/.claude/settings.json now contains "tui": "fullscreen".

  1. Exit, then start a new session with plain claude (no flags, default settings, terminal at least 110 columns wide).
  2. Run /tui with no arguments.

Expected

Current renderer: fullscreen — the save message says the fullscreen renderer will apply to sessions started directly with claude.

Actual

Current renderer: default. Every new session starts on the default renderer; the persisted setting is never applied. Retried repeatedly (bare claude, various flag sets, wide terminals) — always default.

Notes

  • The in-session switch itself works: /tui fullscreen in a running session switches that session, and a pane a plugin opens afterwards is docked beside the transcript. But the choice does not survive to any later session.
  • Sessions started with certain launch flags (for example a custom system prompt) refuse the in-session switch with "Cannot switch renderers in this session — it has restrictions a restart can't carry over". That part may be intended; the setting not applying to fresh sessions looks like the bug.
  • A pane a plugin opened before the switch keeps its inline seat after the switch, while one opened after the switch docks.

Ask

Apply the persisted renderer setting to new sessions started directly with claude, or document what tui in settings.json is meant to control.

View original on GitHub ↗