v2.1.150: scroll wheel no longer scrolls conversation — sends arrow keys instead

Open 💬 31 comments Opened Jun 6, 2026 by tatuliusi

Bug description

After updating to v2.1.150, the mouse scroll wheel no longer scrolls through the conversation output inside the Claude Code TUI. Instead, it sends arrow keys, which cycles through input history in the prompt field.

Previously (before v2.1.150), scroll wheel worked correctly to scroll up/down through the conversation.

A message appears at the bottom of the UI: "Scroll wheel is sending arrow keys · use PgUp/PgDn to scroll" — confirming this is intentional in the new version, but it's a significant UX regression.

Environment

  • Claude Code version: v2.1.150
  • OS: Windows 11 + WSL2 (Ubuntu)
  • Terminal: PyCharm embedded terminal (wsl.exe --distribution Ubuntu)

Expected behavior

Mouse scroll wheel scrolls through conversation output, with a visible scrollbar on the right side of the terminal panel (as it did before v2.1.150).

Actual behavior

Scroll wheel sends arrow keys (navigates input history). No scrollbar visible. Must use PgUp/PgDn to scroll, which is unintuitive and breaks the previous workflow.

Request

Please restore mouse scroll wheel support for scrolling conversation output, or make it configurable.

View original on GitHub ↗

31 Comments

srolel · 1 month ago

I saw this in one chat, but not in others in 2.1.156. resuming the same chat that had this problem in another terminal did not exhibit the issue.

ubunatic · 1 month ago

I have the same issue for a few days.

  • OS: Ubuntu 26.4
  • HW: AMD x86_64
  • Claude: v2.1.168
  • Terminals: Ptyxis (Ubuntu default), Tilix, Foot, Mate Terminal, and others

Scrolling still works in other TUI apps (mc, vim) and worked in claude before.

SuperHuangXu · 1 month ago

Yes, and some keyboards don't even have the PgUp/PgDn keys.

vecalion · 1 month ago
Yes, and some keyboards don't even have the PgUp/PgDn keys.

Like mine 😢 Is there a workaround?

tatuliusi · 1 month ago
> Yes, and some keyboards don't even have the PgUp/PgDn keys. Like mine 😢 Is there a workaround?

Haven't found anything so far, it's so annoying

odefta · 1 month ago

This is so annoying,.... it's not usable at all.

Nordsoft91 · 1 month ago

@claude is there way to rollback/disable? There are plenty of keyboards without PgUp/PgDn so you have to use combinations...

akshay-osmos · 1 month ago

Please provide workaround

tatuliusi · 1 month ago
This one helped me: #12953 (comment)

Confirmed /tui fullscreen then /tui default fixed it for me Thanks!

bayrinat · 1 month ago

The newest version v2.1.169 helped me.

simonkirkham · 1 month ago

Seen in version - Claude Code v2.1.173

bigbitbox · 1 month ago

it is annoying

anorman07 · 1 month ago

Still reproduces on v2.1.174 (current), so this is not yet fixed.

Environment: WSL2 (Ubuntu 24.04), native terminal, TERM=xterm-256color, not in tmux, with "tui": "fullscreen" set in ~/.claude/settings.json.

Symptom: identical to the original report. Mouse wheel up no longer scrolls the transcript; it cycles the prompt input box backward through previously-typed prompts (arrow-key behavior). It appeared on an auto-update and survived a full reboot.

Workaround that restores native terminal scrollback: removing "tui": "fullscreen" from ~/.claude/settings.json (reverting to the default non-fullscreen TUI) lets the terminal handle wheel scrollback again. The trade-off is losing fullscreen rendering. CLAUDE_CODE_DISABLE_MOUSE=1 also disables the mouse capture, but per #66808 and #62294 it leaves scrollback only partly working (full-page granularity, no line-level scroll).

Request: make mouse-wheel transcript scrolling work inside the fullscreen TUI, or expose a dedicated setting to keep wheel events as native terminal scrollback rather than mapping them to input-history navigation.

theyv · 1 month ago

still broken @ cc 2.1.175
tui: default - is a workaround

Erin-LumetraSolutions · 1 month ago

As a work around while we wait for a fix, I found that going to .claude/settings.json and changing tui to "fullscreen", then back to default while the window was open seemed to fix it.

itoolsTim · 1 month ago

I wasn't able to simply switch between fullscreen and default via /tui alone (Claude v2.1.175) but with the help of Claude itself, it told me that it has to do with the renderer being used and that if I did the following it would fix it.

  1. Add the following to your settings.json/settings.local.json
"env": {
    "CLAUDE_CODE_DISABLE_ALTERNATE_SCREEN": "1"
 }
  1. Run "/tui default". This should cause Claude code to reload and pick up the new setting.

Once I did these two things, I am able to get scroll back properly. It does seem to remove things like "jump to the end" feature of the other renderer, but this might be a good solution until it is fixed. I am making a note myself to come back in a few versions and see if it has been fixed to then remove the setting.

I hope it solves the problem for people.

doug-shawhancc · 1 month ago

Honestly, this kind of interface thrashing is kind of worrying. Did anyone look at this and say "yes! our users have been clamoring to use PGUP/PGDN"

mtremsal · 1 month ago

FWIW this is my workaround:

  • DISABLE_MOUSE releases mouse capture, so the wheel goes to the terminal instead of Claude.
  • DISABLE_ALTERNATE_SCREEN keeps output in native scrollback, so there's something for the wheel to scroll.

CLAUDE_CODE_DISABLE_ALTERNATE_SCREEN=1 CLAUDE_CODE_DISABLE_MOUSE=1 claude

rich4756 · 1 month ago

Also seeing it @ cc 2.1.175.
Workaround - Not using TUI

theyv · 1 month ago
FWIW this is my workaround: DISABLE_MOUSE releases mouse capture, so the wheel goes to the terminal instead of Claude. DISABLE_ALTERNATE_SCREEN keeps output in native scrollback, so there's something for the wheel to scroll. CLAUDE_CODE_DISABLE_ALTERNATE_SCREEN=1 CLAUDE_CODE_DISABLE_MOUSE=1 claude

god bless you! :D

odefta · 24 days ago

I can't believe there's no official fix yet for this (very) annoying issue...

keyvez · 22 days ago

Disabled TUI

andrei-dascalu · 21 days ago

Using CLAUDE_CODE_DISABLE_ALTERNATE_SCREEN=1 OR /tui default disables the new renderer.
CLAUDE_CODE_DISABLE_MOUSE=1 just disables mouse interactions (which are awful enough.

I'm guessing the whole feature was done by Claude unsupervised.

nhupham-commonservices · 20 days ago

type /tui default to fixed

dblackburn-atomic · 19 days ago

Also hitting this on macOS

  • OS: macOS (Darwin 24.6.0)
  • IDE: PyCharm 2025.2
  • Claude Code JetBrains plugin: 0.1.14-beta
  • CLI: reproduces on 2.1.179 and after upgrading to 2.1.193

It's annoying as hell. Please fix

anatoly-pashin-axon21 · 17 days ago

If you use Warp on MacOS:

  1. open settings
  2. features
  3. in the "Terminal section" enable the options "Enable Mouse Reporting" and "Enable Scroll Reporting"
  4. restart Claude
  5. now /tui fullscreen works good and mouse scroll scrolls the view, not the commands history
ryanscovill · 17 days ago

Found that on MacOS the issue appears with some third party scrolling apps like Smooze and SmoothScroll as they send arrow key events. Disabling animation with these apps and sending scroll events fixes the issue.

dp1140a · 13 days ago

/tui default fixed it for me. The new mouse interactions are awful. Every time I clicked in the window to get focus it would interpret that as an answer to a question. I want to scroll to view conversation not, scroll in the input box. I turned off all the mouse interactions. Yeah it does look like Claude coding Claude without a human looking at it and saying yeah that sucks.

carsonmulligan · 13 days ago

why would i ever want to scroll through prompts instead of using the arrow keys? roll this back please

srsholmes · 1 day ago

Thsi desperatly needs fixing. it makes the cli unusable.