›_ Claude Code Issues
Claude Code Issues / #12953

[BUG] Mousewheel scrolls through input history instead of chat history

Open 💬 18 comments Opened Dec 3, 2025 by Sp33dyFoX

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)
  • [x] I am using the latest version of Claude Code

What's Wrong?

  • Claude Code version: 2.0.57
  • Running via SSH in Windows PowerShell
  • Mousewheel scrolls through previous input messages instead of scrolling the conversation
  • Page Up/Page Down also cycle through input history
  • Started after a watch command was run in a Bash tool call
  • Persists after restart and reinstall

What Should Happen?

When using the mousewheel or Page Up/Page Down keys, the chat conversation history should scroll up and down, not cycle through previously typed input messages.

Error Messages/Logs

No specific error messages related to the scroll bug. The debug logs just show normal operations.

  Environment:
  - Claude Code version: 2.0.57
  - OS: Windows (PowerShell via SSH to Linux server)
  - Terminal: Windows PowerShell

  Additional context:
  - Issue started after a watch command was executed via the Bash tool
  - Reinstalling Claude Code did not fix the issue
  - Other PowerShell windows work normally
  - No error messages in ~/.claude/debug/ logs related to this issue

Steps to Reproduce

  1. Open Windows PowerShell
  2. SSH into a Linux server
  3. Run claude to start Claude Code
  4. Ask Claude to monitor something using the watch command in a Bash tool call (e.g., watch -n 2

"some command" run in the background)

  1. The background watch process runs and outputs terminal escape sequences
  2. Kill the watch process
  3. Mousewheel scroll now cycles through input history instead of scrolling chat
  4. Exit Claude Code and restart - issue persists
  5. Reinstall Claude Code (npm i -g @anthropic-ai/claude-code) - issue persists
  6. Close PowerShell window, open new one, SSH again, run claude - issue persists

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.0.57

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

PowerShell

Additional Information

Everything was working fine until it wasn't. I asked Claude to assess what led up to the issue and it told me the "watch" command has a bug.

View original on GitHub ↗

18 Comments

github-actions[bot] · 7 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/2301
  2. https://github.com/anthropics/claude-code/issues/10645
  3. https://github.com/anthropics/claude-code/issues/10010

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

Sp33dyFoX · 7 months ago

Nah, this is not a duplicate issue. Those other issues share a similar type of issue, but the series of events that led up to their issues are not the same as the series of events which led up to my issue.

What happened:
-Claude used the "watch" command to monitor the activity of something that was processing within my project.

Why it broke things:

  • watch uses an alternate screen buffer - it sends special terminal escape codes to switch the

terminal into a different display mode

  • When Claude killed the process, it didn't cleanly exit and restore the terminal to its normal state
  • Those escape codes corrupted how Claude Code's terminal interface handles input/scrolling
  • The corruption somehow persisted into Claude Code's internal state, which is why restarting

doesn't fix it

Sp33dyFoX · 7 months ago

My server crashed and somehow the problem fixed itself on my end. But it should be known that the series of events that occurred were what caused the initial scrolling problem in the first place. You can mark this as resolved or archived or whichever as long as the developers are made aware of the potential recurring issue.

github-actions[bot] · 6 months ago

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.

giodigital · 5 months ago

the problem are not solved

ism · 4 months ago

still not resolved. it appears in latest version 2.1.56

polarbaryon · 4 months ago

Just appeared for me in 2.1.71. Not resolved.

IBlanco97 · 3 months ago

Not resolved. I have the same issue

IBlanco97 · 3 months ago

Solution from this post: https://www.reddit.com/r/ClaudeCode/comments/1rdwpdb/terminus_not_scrolling/?tl=es-419

Jason-Terry · 3 months ago

Not fixed... occours on windows 11, wave terminal.

polarbaryon · 3 months ago
Just appeared for me in 2.1.71. Not resolved.

Figured out the cause for this: was running tix for shell stability and it was intercepting wheel movement. Could probably configure tix but decided on another container route that worked better overall.

akostibas · 1 month ago

This just started happening for me out of the blue, v2.1.139. No me gusta.

macOS, terminal.app, zsh.

akostibas · 1 month ago

Found a workaround: /tui fullscreen (which explicitly enters the mode I don't like) followed by /tui default.

It seems the TUI mode gets "confused", thinking that it is in the default mode even when it's not, or something like this. Explicitly switching to fullscreen and then back gets me back into default mode: the chat history is back in the term, and scrolling does what I want.

ubunatic · 1 month ago

Still broken in v2.1.168 (Ubuntu 26.4, Tilix, Ptyxis, and other Terminal apps).
Please fix it, this is a real UX killer!

epsilver · 1 month ago
Found a workaround: /tui fullscreen (which explicitly enters the mode I don't like) followed by /tui default. It seems the TUI mode gets "confused", thinking that it is in the default mode even when it's not, or something like this. Explicitly switching to fullscreen and then back gets me back into default mode: the chat history is back in the term, and scrolling does what I want.

This saved my life. I experienced this bug on Fable 5 leftover context, so I was about to cry.

foolish-pup · 1 month ago
找到了一个解决方法： /tui fullscreen （这会明确进入我不喜欢的模式），然后是 /tui default 。 似乎 TUI 模式出现了“混乱”，它误以为自己处于默认模式，即使实际上并非如此。手动切换到全屏模式再切换回来就能恢复到默认模式：聊天记录会重新显示，滚动功能也能正常工作了。

感谢！

marnon-godaddy · 29 days ago
Found a workaround: /tui fullscreen (which explicitly enters the mode I don't like) followed by /tui default. It seems the TUI mode gets "confused", thinking that it is in the default mode even when it's not, or something like this. Explicitly switching to fullscreen and then back gets me back into default mode: the chat history is back in the term, and scrolling does what I want.

Also saved my life. Thank you!

spiveym · 7 days ago

This needs fixing still. v2.1.205