[BUG] TUI welcome screen shows stale model/effort after in-session /model+/effort changes followed by /compact

Resolved 💬 3 comments Opened Mar 24, 2026 by Stephen-C-Noh Closed Mar 27, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [ ] I am using the latest version of Claude Code

What's Wrong?

Title: TUI welcome screen shows stale model/effort after in-session /model+/effort changes followed by /compact

Version: Claude Code v2.1.79

Actual:
The welcome screen shows the pre-revert values: Opus 4.6 with max effort

<img width="1920" height="1032" alt="Image" src="https://github.com/user-attachments/assets/8f17589e-9a13-479a-a5e0-d8b74360f635" />

Root cause hypothesis:
/compact appears to snapshot or cache the model/effort state at some point during the session (possibly when the last major context event occurred), rather than reading the live current values when re-rendering the welcome screen.

Settings file (~/.claude/settings.json) at time of bug:
{
"model": "sonnet",
"effortLevel": "medium"
}

What Should Happen?

Expected:
The welcome screen shows the current active settings: Sonnet 4.6 with medium effort

Error Messages/Logs

Steps to Reproduce

Steps to reproduce:

  1. Start a session (default or any model/effort)
  2. Run /model opus and /effort max mid-session (e.g., for planning)
  3. After planning, run /model sonnet and /effort medium to revert — changes take effect immediately in-session
  4. Run /compact
  5. Observe the welcome screen header after compact completes

Claude Model

Other

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.79

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

WSL (Windows Subsystem for Linux)

Additional Information

<img width="1920" height="1032" alt="Image" src="https://github.com/user-attachments/assets/c45f70d0-02e2-4f22-8556-995c0a967c78" />

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗