[BUG] Claude Code output ALWAYS cut-off in new "scrolling window" feature

Status Fixed / completed
Reported on v2.1.162
Maintainer reply None cached
Activity 3 comments · opened Jun 5, 2026 · closed Jun 8, 2026

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?

It seems like you changed how you scroll through messages in a Claude Code terminal session and it is completely cut-off I can't see most of my message history anymore. I can't scroll up, it's just an empty spot with some agent output, sort of the equivalent to tailing a file essentially. Even when I /exit and go back in. Makes it very difficult to know what the agent is doing....

What Should Happen?

I should be able to scroll up and see my/the agent's message history

Error Messages/Logs

Steps to Reproduce

Use Claude Code in the terminal and send enough messages that you have to scroll

Claude Model

Opus

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

2.1.162

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

3 Comments

github-actions[bot] · 4 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/9001
  2. https://github.com/anthropics/claude-code/issues/42002
  3. https://github.com/anthropics/claude-code/issues/28077

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

ggrillone · 4 months ago

seems fixed now

github-actions[bot] · 2 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.