[BUG] Scrolling Claude Response with Keyboard Stopped Working

[joellogic]

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?

Keyboard arrow key scrolling through Claude responses stopped working in the desktop app (Windows 11) as of April 14, 2026. Previously I could scroll through responses using arrow keys, now it no longer responds to them.
I am on a laptop, no mouse, so not being able to scroll with the keyboard arrows is super inconvenient as I have some very long Claude responses

What Should Happen?

Arrow keys should scroll Claude responses.

Error Messages/Logs

Steps to Reproduce

Chat with Claude
Make a request
Claude replies
Click in the response area
navigate / scroll with keyboard arrows keys - nothing happens

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

Claude 1.2581.0 (f10398) 2026-04-14T17:16:40.000Z

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Other

Additional Information

No response

[anhphamduy]

im facing the same issue. on both mac and my ubuntu vm, when I go to rewind the arrow keys don't work. Neither does the ESC key.

[0xbrainkid]

This is navigation-integrity failure on a core inspection path.

If keyboard scrolling of Claude responses stops working, the user loses a primary way to inspect long outputs precisely — especially in accessibility-heavy or keyboard-first workflows. That turns ordinary reading and verification into a friction problem, but also a trust problem when users can no longer efficiently examine the full record.

Why it matters:

• long responses, logs, and diffs are often only useful if you can traverse them accurately
• keyboard navigation is not a nice-to-have for many users; it is the main control surface
• once navigation breaks, the visible transcript becomes harder to audit even if the data technically still exists

I would want clarity on:

1. whether the regression is in focus handling, keybinding dispatch, scroll container ownership, or virtualization/rendering
2. whether mouse scrolling still works while keyboard events are dropped
3. whether the failure affects only response panes or any long content surface in the app

In agent tools, inspection is part of control. If users cannot reliably move through the record, the evidence trail becomes materially less usable.

[plilley2020]

Same issue. Using the scroll bar is terrible; it's thin, hard to grab, and makes the window scroll at a wildly fast pace with no ability to stop precisely where needed. It makes Claude Cowork nearly unusable.

[ghager68]

This issue is severely impeding me with Claude 1.7196.0 on macOS Tahoe 26.4.1. I agree with the prior comments. Very frustrating.

[matiasregalo]

Same issue on Windows with Claude Desktop version 1.7196.0 . Arrow keys don't scroll the chat thread after clicking on a response. Page Up/Down also doesn't work. Only the scrollbar and mouse wheel work. This is a real pain on a laptop without a mouse.

[builder-main]

In our case everything broke today, up/down scroll through history, mouse scroll does nothing, scroll bar not appearing in claude console (VSCode terminal, Rider Terminal both under git bash)