[BUG] Terminal scrolls to the top after each response

Status Fixed / completed
Maintainer reply None cached
Activity 4 comments · opened Nov 17, 2025 · closed Nov 17, 2025

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?

  • Terminal scrolls to top after each response
  • You have to manually scroll down to read the output
  • Your OS: macOS (Darwin 25.1.0)

What Should Happen?

Stop trying to show all history before displaying the response. Simply just display the response.

Error Messages/Logs

Steps to Reproduce

open up any terminal window, try to do anything with claude cli. you end up at the top of the window every time and have to scroll to the bottom to see the response.

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.0.42

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

4 Comments

github-actions[bot] · 11 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/826
  2. https://github.com/anthropics/claude-code/issues/10769
  3. https://github.com/anthropics/claude-code/issues/1486

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

GrahamCampbell · 11 months ago

Indeed, this is a duplicate of #826 and can be closed out.

equilibrium-eq · 11 months ago

We are closing this, although Its not quite a duplicate, this happens right out of the box, and doesn't require a large context. It's just all context windows of any size for us.

github-actions[bot] · 10 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.