claude-code - 💡(How to fix) Fix Transcript view lacks internal scrolling — unusable via keyboard, relies on terminal backbuffer [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#48002Fetched 2026-04-15 06:36:09
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Timeline (top)
labeled ×3commented ×1

Root Cause

  1. Mouse/trackpad scrolling only works indirectly. In tmux with mouse on, trackpad scrolling works but only because tmux is scrolling its own backbuffer — not because Claude Code is handling it. With mouse off (a common tmux config), nothing scrolls at all.
RAW_BUFFERClick to expand / collapse

Problem

The Transcript view (Ctrl+O) has no internal scroll handling. It relies entirely on the terminal emulator or multiplexer (e.g., tmux) to scroll the rendered output. This means:

  1. No keyboard scrolling at all. Arrow keys, Page Up/Down, and custom keybindings in the Scroll context have no effect. The Scroll context is documented as applying to "fullscreen layout" which doesn't appear to exist in the CLI.

  2. Mouse/trackpad scrolling only works indirectly. In tmux with mouse on, trackpad scrolling works but only because tmux is scrolling its own backbuffer — not because Claude Code is handling it. With mouse off (a common tmux config), nothing scrolls at all.

  3. Long conversations are inaccessible. Because scrolling depends on the tmux/terminal backbuffer (which has a finite history-limit), earlier parts of a long conversation cannot be reached in the Transcript view.

Expected behavior

The Transcript view should handle scrolling internally, like less or any well-behaved TUI application. It should:

  • Support keyboard scrolling (at minimum arrow keys, Page Up/Down)
  • Respect the Scroll context keybindings (e.g., ctrl+f/ctrl+b for page scroll, ctrl+u/ctrl+d for half-page)
  • Not depend on the terminal's backbuffer for scroll range

Environment

  • Claude Code CLI in Alacritty + tmux (also tested in macOS Terminal.app)
  • macOS

extent analysis

TL;DR

Implement internal scroll handling in the Transcript view to support keyboard scrolling and respect the Scroll context keybindings.

Guidance

  • Review the Scroll context documentation to understand the intended behavior and identify potential discrepancies with the current implementation.
  • Investigate how other TUI applications, such as less, handle scrolling internally to inform the design of the Transcript view's scroll handling.
  • Consider adding support for keyboard scrolling using arrow keys, Page Up/Down, and custom keybindings in the Scroll context.
  • Evaluate the feasibility of decoupling the Transcript view's scroll range from the terminal's backbuffer to ensure accessibility of long conversations.

Example

No code snippet is provided as the issue lacks specific implementation details.

Notes

The solution may require significant changes to the Transcript view's implementation, and careful consideration of the Scroll context's behavior is necessary to ensure consistency with the application's documentation.

Recommendation

Apply a workaround by using a terminal emulator or multiplexer that supports scrolling, such as tmux with mouse on, until internal scroll handling is implemented in the Transcript view. This allows for some level of scrolling functionality, although it may not meet the expected behavior.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

The Transcript view should handle scrolling internally, like less or any well-behaved TUI application. It should:

  • Support keyboard scrolling (at minimum arrow keys, Page Up/Down)
  • Respect the Scroll context keybindings (e.g., ctrl+f/ctrl+b for page scroll, ctrl+u/ctrl+d for half-page)
  • Not depend on the terminal's backbuffer for scroll range

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING