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

[Sp33dyFoX]

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?

- 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)
5. The background watch process runs and outputs terminal escape sequences
6. Kill the watch process
7. Mousewheel scroll now cycles through input history instead of scrolling chat
8. Exit Claude Code and restart - issue persists
9. Reinstall Claude Code (npm i -g @anthropic-ai/claude-code) - issue persists
10. 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.

[github-actions]

Found 3 possible duplicate issues:

1. [BUG] Can't inspect previously generated content. Key up, key down and mouse scroll are not working. #2301
2. [Bug] Scroll input bound to message history prevents viewing previous results #10645
3. Scrolling over mosh connection cycles through input history instead of conversation history #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]

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]

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]

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]

the problem are not solved