Cannot scroll up in Windows Terminal while Claude Code is running (regression since 2.1.x / Opus 4.7 release)

Status Closed — not planned

Reported on v2.1.112

Maintainer reply None cached

Activity 4 comments · opened Apr 21, 2026 · closed May 28, 2026

Summary

Since the Claude Code release that introduced Opus 4.7 support, scrolling
the terminal scrollback is completely blocked while the Claude Code TUI
is running in Windows Terminal. Mouse wheel, Shift+PageUp, and scrollbar
drag all do nothing. The only way to see earlier output is to exit Claude
Code.

This is a regression — scrolling worked normally in prior versions.

Environment

Claude Code: 2.1.112
Windows Terminal: 1.24.10921.0
OS: Windows 11 Pro for Workstations, build 26200
Shell: PowerShell / bash via Git for Windows (same behavior in both)

Repro

Open Windows Terminal
Run claude
Produce enough output to require scrollback (any long task)
Try to scroll up — mouse wheel, Shift+PageUp, scrollbar drag

Expected

Normal terminal scrollback while the TUI is running, as in prior versions.

Actual

Scroll inputs are ignored. Scrollback is inaccessible until Claude Code exits.

Notes

Ctrl+O in-app transcript viewer is a partial workaround but doesn't
replace being able to scroll the terminal naturally (e.g. to copy older
tool output).

View original on GitHub ↗

4 Comments

github-actions[bot] · 4 months ago

Closing for now — inactive for too long. Please open a new issue if this is still relevant.

pohy · 3 months ago

Still happening for me. Scrolling via mouse scroll wheel just "browses" prompt history.

brizzlyadams · 2 months ago

I'm seeing what might be a related manifestation of this on Windows: after quitting Claude Code (/exit or Ctrl+C), leftover TUI chrome — specifically the "trust this folder" banner — stays in the terminal scrollback instead of the prompt cleanly restoring. This didn't happen in earlier versions, so it reads as a regression, same as this issue.

Diagnostic notes, ruling out environment as the cause:

Version: 2.1.220
Shell version — reproduces on both:
Windows PowerShell 5.1.26100.8894 (Desktop edition)
PowerShell 7.6.4 (Core edition)
Terminal host — reproduces on both:
Windows Terminal (WT_SESSION set)
Legacy conhost.exe (forced via Windows Terminal → Settings → Startup → Default terminal application → "Windows Console Host")
OS: Windows 11 (build 10.0.26200)

Since both shell version and terminal host are ruled out, this points to Claude Code's own exit/cleanup logic (alt-screen-buffer handling not clearing the trust-dialog render on exit) rather than a local config issue — possibly the same root cause as the scroll-lock behavior reported here.

github-actions[bot] · 20 days ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.