You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug] Terminal auto-scrolls to buffer start when model writes output during scroll-up #35415
Bug Description
In a windows console (Windows 11 "new" terminal), if we scroll up a little bit to sneak what recently happend in the session while the model is working, as soon something new is written by the model, the terminal is getting scrolled all the way up to the very beginning of the buffer. That's extremely annoying.
Environment Info
Platform: win32
Terminal: windows-terminal
Version: 2.1.77
Feedback ID: aad02164-1782-428e-9db9-161ecaa70ecc
Reacted by Joachim, Robin, Brett Woodward, SnowOnTheMountain and Ahmet Sezen
Auto-scroll to bottom on output — Windows Terminal has a setting for this: Settings → Profiles → Defaults → Advanced → toggle off "Automatically scroll to bottom on output". This stops the terminal from chasing new output when you are scrolled up reading history.
Scroll to buffer start — this is a different issue. Claude Code uses cursor positioning escape sequences (\e[H cursor home, \e[s/\e[u save/restore cursor) during status line updates and streaming. Some of these can reset the viewport position to the top of the scrollback buffer rather than just the bottom. This is the more disruptive of the two behaviors.
For (2), the most reliable workaround is running Claude Code inside tmux or Windows Terminal tabs with separate scroll buffers. tmux isolates the escape sequences to the inner pane, so your outer scrollback is not affected. You can scroll the tmux buffer with prefix + [ while Claude keeps working.
# Quick tmux setup
tmux new -s claude
# Inside tmux, run claude
# Scroll: Ctrl+B then [ then arrow keys
# Exit scroll: q
This was fixed in v2.1.101 — Stopped emitting ERASE_SCROLLBACK (CSI 3J) on full resets in non-fullscreen mode, so terminal scrollback is preserved instead of being wiped (which made the view appear to jump to the top of the session) during streaming. If you're still seeing this in the latest version, please comment with your version and repro and we'll reopen.
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.
Activity
github-actions commentedon Mar 17, 2026
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
yurukusa commentedon Mar 17, 2026
Two things happening here:
Auto-scroll to bottom on output — Windows Terminal has a setting for this: Settings → Profiles → Defaults → Advanced → toggle off "Automatically scroll to bottom on output". This stops the terminal from chasing new output when you are scrolled up reading history.
Scroll to buffer start — this is a different issue. Claude Code uses cursor positioning escape sequences (
\e[Hcursor home,\e[s/\e[usave/restore cursor) during status line updates and streaming. Some of these can reset the viewport position to the top of the scrollback buffer rather than just the bottom. This is the more disruptive of the two behaviors.For (2), the most reliable workaround is running Claude Code inside tmux or Windows Terminal tabs with separate scroll buffers. tmux isolates the escape sequences to the inner pane, so your outer scrollback is not affected. You can scroll the tmux buffer with
prefix + [while Claude keeps working.ashwin-ant commentedon Apr 19, 2026
This was fixed in v2.1.101 — Stopped emitting ERASE_SCROLLBACK (CSI 3J) on full resets in non-fullscreen mode, so terminal scrollback is preserved instead of being wiped (which made the view appear to jump to the top of the session) during streaming. If you're still seeing this in the latest version, please comment with your version and repro and we'll reopen.
github-actions commentedon Apr 26, 2026
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.