[BUG] Can't inspect previously generated content. Key up, key down and mouse scroll are not working.
Open 💬 31 comments Opened Jun 19, 2025 by heyagent
Environment
- Platform: Claude Code Max
- Claude CLI version: 1.0.29 (Claude Code)
- Operating System: Windows 11 WSL2
- Terminal: Windows Terminal
Bug Description
When I'm using the key up or key down or when I'm scrolling with the mouse, instead of having the terminal content go up and down, I'm having the events sent to the prompt input. So if I click up, I go up in messages, if I click down, I go down in messages, and if I scroll up or down, it is the same behavior.
Steps to Reproduce
- Execute a prompt
- Try to scroll up so you can understand and see the generated content.
- Moving up or down is not supported and only the prompt keeps getting changed as we have focused only on the message input.
Expected Behavior
I expect to be able to see the entire content as long as it is in history as I scroll up or down.
Actual Behavior
The prompt message keeps getting changed and I can't move the content in the terminal up or down.
Additional Context
Started happening at 1.0.27 version. Sometimes I'm getting IDE disconnected but I'm not sure if it is related to this bug.
31 Comments
facing the same issue
Same issue. Facing it in Terminal, Terminus, VSCode, and Putty. Claude Code is running on Armbian 25.5.1 Bookworm 6.1.115 minimal.
On my mac terminal, I fixed this by going into Terminal -> Settings -> Profiles -> Keyboard -> Uncheck the box at the bottom for "Scroll alternate screen"
I'm getting the same thing with some agents. Weird part is it's just for that agent, not convo specific. Even tried opening in a different type of terminal, same thing. Once solution, move the agent's folder to a new location, start a new convo and it is back to normal. very annoying.
I too am experiencing the same issues in Tliex, Gnome Term, tmux, screen
Same issue on alacritty
claude Version: 2.0.11
Same issue on alacritty
claude ver: 2.0.14
This has seriously interrupted my workflow. For fellow travelers I was able to use the Claude Code for VS Code extension to /resume previous conversations and scroll up and access important info and continue working.
Update next day: its working in alacritty, cannot reproduce bug
Facing the same. Very frustrating. Only when using it with tmux
I’m getting the same issue irrespective of the terminal I use if Claude code is running inside a tmux session - which is my main use case
A workaround is to ctrl + B then [
This will enable your cursor to scroll the content using the keyboard up/down arrows (or the wheel)
Click q to exit this mode.
Reproducible on ghostty as well
happening in vscode claude extension for me now
It suddenly is happening to me since today also. Before I had no problems. Is it in a pushed update or something?
Using Ghostty.
same here, claude again unusable !
Started happening to me as well this week, even on short conversation. I now have no ability to go back and look at message history.
The only workaround I can find it to open wsl via a PowerShell terminal.
Windows 11 with Windows Terminal - WSL (Ubuntu 22.04)
In Cursor if I use a claude code remotely via ssh I have this issue as well as of the past few days. If I run claude code in a local terminal shell from Cursor it scrolls normally and I can see the message history.
WORKAROUND:
I did find that if I ssh from Terminal.app on my mac and then run it, claude code scrolls normally.
This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.
https://github.com/anthropics/claude-code/issues/9902
Releated issue complaining about seeing this problem when using tmux (me too).
This is still happening to me regardless of which terminal I use. Built into VS code, iTerm, Ghostyy.
Claude Code version 2.1.19
Have you guys tried using copy mode?
CTRL+A, and then ESC.
Then try scrolling.
Still happening. I was so excited to run 10 agents with tmux but I can't scroll up to see the plans...
Codex solves this very easily with a
ctlr + tbind to see transcript.If you're still running into this issue you can try:
echo "set -g mouse on" >> ~/.tmux.conf && tmux source-file ~/.tmux.confIn tmux,
ctrl + Bthen:enables the command mode.Then you can type the aforementioned
set -g mouse onto unblock your current session.i am not using tmux and also having this issue, Claude Code v2.1.69
This is annoying, when is this gonna get fixed!!!
This scrolling issue is part of a broader pattern (#826, #769, #1486, #367, #33814) where Claude Code's TUI rendering causes unintended scroll behavior.
Workaround 1 — tmux isolates scrolling:
tmux manages its own viewport independently of the terminal's scroll buffer. Scroll with
Ctrl+B [in tmux instead of using the terminal's native scroll.Workaround 2 — Compact to reduce rendered history:
Less conversation history = less content to render = less scrolling issues. Compact at natural breakpoints.
Workaround 3 — Reduce terminal scrollback:
Smaller scrollback buffers reduce the range of scroll-jumping.
Workaround 4 — Fresh sessions for new tasks:
Workaround 5 — Use headless mode for non-interactive work:
No TUI = no scrolling issues.
Mouse Scroll Drops Text Selection on Windows (v2.1.89)
Specific symptom not covered in this thread: when selecting text to copy, scrolling with the mouse wheel releases the selection entirely. The selected text is deselected and the copy fails.
This does NOT happen in any other application on the same machine -- only in Claude Code. The TUI's mouse event capture (escape sequences for mouse tracking) is intercepting the scroll event during selection, which the terminal interprets as a selection-cancel.
Reproduction:
Expected: Terminal handles scroll-during-selection natively (as every other CLI application does).
Impact: Cannot copy any output that spans more than one visible screen. Combined with the Unicode mojibake on paste (#34247) and the alt-screen history wipe (#42192), the copy/paste workflow on Windows is essentially broken on v2.1.89.
Environment: v2.1.89, Windows 11, Windows Terminal, PowerShell
Weirdly for me mouse wheel scrolling works fine in "claude agents", but not in just "claude" - so my workaround is to just "/background" the session and open it in the agents view instead.
this is really annoying. when i scroll up i do not see the previous chunk of the convesation, but rather some older part of the conversation. and i keep telling opus to stop being so damn verbose, but it keep on going.
mac, iterm. any other apps work in the terminal.
i know you guys vibe code a lot, but you should start testing it as well.
type left arrow to escape from the input box for temp.
Root cause + fix (anyone on v2.1.89+):
If your mouse wheel / arrow keys scroll Claude Code's own conversation (or cycle the input history) instead of your terminal's scrollback, it's because fullscreen rendering is active. It draws the UI on the terminal's alternate screen buffer (like
vim/htop) and captures mouse events, so the terminal's native scrollback never sees the wheel.Fix — switch back to the classic renderer:
/tui default— takes effect immediately, persists to~/.claude/settings.json, and your conversation stays intact.~/.claude/settings.json:``
json
`{ "env": { "CLAUDE_CODE_DISABLE_ALTERNATE_SCREEN": "1" } }
Cmd/Ctrl+F`, and tmux copy mode work as before.The classic renderer keeps the conversation in your terminal's native scrollback, so the wheel,
Keep flicker-free fullscreen but free the mouse: set
CLAUDE_CODE_DISABLE_MOUSE=1(keeps fullscreen; scroll Claude's view withPgUp/PgDn, terminal handles selection).tmux users: fullscreen needs
set -g mouse onin~/.tmux.conffor the wheel to reach Claude Code.Docs: https://code.claude.com/docs/en/fullscreen
Tradeoff: the classic renderer loses the fixed-bottom input box / flat memory of fullscreen, but restores normal terminal scrolling.