anthropics
[BUG] Can't inspect previously generated content. Key up, key down and mouse scroll are not working.
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.
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.
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
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.
It suddenly is happening to me since today also. Before I had no problems. Is it in a pushed update or something?
Using Ghostty.
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.
