claude-code - 💡(How to fix) Fix [BUG] TUI scrollback corrupts permanently when a fullscreen app changes the monitor resolution (Windows / Cursor terminal, no reflow on resize)

Preflight Checklist

• I have searched existing issues and this hasn't been reported yet
• 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?

When I launch a separate fullscreen application that forces a monitor resolution different from my desktop resolution, the entire Claude Code TUI scrollback — every prior message in the session — becomes visually corrupted, and it stays corrupted afterward. My monitor runs at 2K (2560×1440). When I open an app that forces 1080p (1920×1080) in exclusive fullscreen — e.g. the old PopCap Zuma, which forces 1080p — and then return to the terminal, all previously rendered output is mangled:

Text laid out at the old width is re-broken into wrong, often very narrow line breaks. This is not just a column-count change — long paragraphs become jagged. Tables, boxes, and other box-drawing / visual elements break apart and no longer line up. The corruption applies retroactively to all earlier messages in the session, not just new output.

It does not auto-recover. Crucially, this only happens when there is a resolution mismatch — fullscreen apps that run at my native resolution do not trigger it. So the trigger is the change in resolution (which resizes the terminal's character grid), not fullscreen itself.

What Should Happen?

After the monitor resolution changes (and the terminal's reported dimensions change), Claude Code should redraw/reflow its output cleanly without retroactively mangling previously rendered messages, tables, and visual elements. Prior scrollback should remain readable.

Error Messages/Logs

Steps to Reproduce

Set the monitor to a high resolution (mine is 2560×1440 / "2K"). Open Claude Code in the Cursor integrated terminal and have a conversation with enough output to fill scrollback, ideally including a markdown table or other box-drawn/visual element. Launch a fullscreen application that forces a different resolution (e.g. PopCap Zuma, which forces 1920×1080) in exclusive fullscreen. Exit the app / Alt-Tab back to the desktop so the monitor returns to its native resolution. Look at the Claude Code terminal: all previously rendered messages, tables, and visual elements are now corrupted, and stay that way.

Note: launching a fullscreen app that runs at the native resolution does not reproduce it — the resolution mismatch is required.

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

2.1.150 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Cursor

Additional Information

Key diagnostic detail: the corruption only occurs on a resolution mismatch. A fullscreen app running at my native resolution never triggers it — only an app that forces a different resolution (e.g. PopCap Zuma forcing 1080p on a 1440p monitor) does. Likely cause (hypothesis): a monitor resolution change resizes the terminal's character grid, firing a terminal resize event (SIGWINCH on Unix; the ConPTY / console buffer-resize equivalent on Windows). It looks like the TUI re-renders at the new dimensions but does not correctly reflow/re-wrap the already-committed scrollback lines that were hard-wrapped at the previous width — so previously drawn content (especially tables and box-drawing characters) ends up permanently broken. Related existing issues (none cover this trigger or the Windows/Cursor environment):

#58906 — Terminal UI becomes corrupted after resizing window (macOS, manual resize) #8276 — Text doesn't reflow when terminal is resized from narrower to wider (iTerm2/macOS) #49086 — Terminal resize causes repeated banner/content duplication in scrollback (per-frame redraw leak) #57145 — Terminal resize causes content duplication and display corruption (macOS)