starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Flickering/rapid scroll from top to bottom for every character output or typed/random scrolls to top #23991

New Issue
Closed
opened 2026-01-31 08:58:23 +00:00 by claunia · 1 comment
claunia commented 2026-01-31 08:58:23 +00:00
Owner
Copy Link

Originally created by @Caleb-KS on GitHub (Jan 23, 2026).

Windows Terminal version

1.23.13503.0

Windows build number

10.0.26100.7623

Other Software

While running common REPLs (Ink) or Claude Code, sometimes the terminal tab gets into a state where it rapidly scrolls to the top and all the way back down in the terminal history for every character typed or output while the REPL is running.

I am not sure how to reproduce it, but it happens sooner or later. Once a tab is "infected" it doesn't recover. I've played with hardware acceleration settings and other settings that seem related. Nothing affects it that I can tell.

If you look at the Claude Code github issues, you will see multiple people have submitted issues.

The weird thing is I don't think it's only Claude Code, since I had Claude Code write a REPL to do something else (it used Ink as the framework) and it also had the issue.

FWIW I have a HP ZBook 15 G9 with Intel and Nvidia graphics cards.

Steps to reproduce

Use Claude Code in a Windows Terminal tab for a while.

Expected Behavior

No response

Actual Behavior

Scrolling rapidly from top to bottom of terminal history.

Or just random scroll all the way to the top and stay there.

Originally created by @Caleb-KS on GitHub (Jan 23, 2026). ### Windows Terminal version 1.23.13503.0 ### Windows build number 10.0.26100.7623 ### Other Software While running common REPLs (Ink) or Claude Code, sometimes the terminal tab gets into a state where it rapidly scrolls to the top and all the way back down in the terminal history for every character typed or output while the REPL is running. I am not sure how to reproduce it, but it happens sooner or later. Once a tab is "infected" it doesn't recover. I've played with hardware acceleration settings and other settings that seem related. Nothing affects it that I can tell. If you look at the Claude Code github issues, you will see multiple people have submitted issues. The weird thing is I don't think it's only Claude Code, since I had Claude Code write a REPL to do something else (it used Ink as the framework) and it also had the issue. FWIW I have a HP ZBook 15 G9 with Intel and Nvidia graphics cards. ### Steps to reproduce Use Claude Code in a Windows Terminal tab for a while. ### Expected Behavior _No response_ ### Actual Behavior Scrolling rapidly from top to bottom of terminal history. Or just random scroll all the way to the top and stay there.
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 08:58:23 +00:00
claunia commented 2026-01-31 08:58:24 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Jan 23, 2026):

Let me preface this with a tl;dr: This is not a bug in our terminal. Copilot CLI and Claude Code are simply poorly written right now - seriously.

The shortest description for, what a terminal is, is: A terminal is basically a text editor. Yep, that's it.
So, here's how Claude Code works, to my current knowledge:

  • Every time you type something or do something, it re-renders everything
  • When it re-renders, it erases the entire text buffer (= like pressing Ctrl+A & Delete in a text editor)
  • Then it re-prints everything (= like pressing Ctrl+V to paste your clipboard)

Imagine you do "Ctrl+A, Delete, Ctrl+V" in that order in your favorite text editor. No matter how fast you do that, you'll have brief period where the text editor is completely empty. And if you paste a ton of text with Ctrl+V, you may even have to wait a bit before the text is pasted. Because of this, there's nothing you can do to fix this. This will happen in any terminal, on any hardware, because fundamentally the issue is how Claude Code renders itself.

The solution is for Claude Code is to either stop using Ink, which really isn't a great TUI framework to begin with, or to start using something like ink-virtual-list, which will put large amounts of text into a virtual scroll view.

FWIW, Copilot CLI has a slightly different issue, but is fundamentally the same, as they also use Ink (unfortunately). The good news is that they're working on using something like ink-virtual-list.

@lhecker commented on GitHub (Jan 23, 2026): Let me preface this with a tl;dr: This is not a bug in our terminal. Copilot CLI and Claude Code are simply poorly written right now - seriously. The shortest description for, what a terminal is, is: A terminal is basically a text editor. Yep, that's it. So, here's how Claude Code works, to my current knowledge: * Every time you type something or do something, it re-renders everything * When it re-renders, it erases the entire text buffer (= like pressing Ctrl+A & Delete in a text editor) * Then it re-prints everything (= like pressing Ctrl+V to paste your clipboard) Imagine you do "Ctrl+A, Delete, Ctrl+V" in that order in your favorite text editor. No matter how fast you do that, you'll have brief period where the text editor is completely empty. And if you paste a ton of text with Ctrl+V, you may even have to wait a bit before the text is pasted. Because of this, there's nothing you can do to fix this. This will happen in any terminal, on any hardware, because fundamentally the issue is how Claude Code renders itself. The solution is for Claude Code is to either stop using Ink, which really isn't a great TUI framework to begin with, or to start using something like [`ink-virtual-list`](https://github.com/archcorsair/ink-virtual-list), which will put large amounts of text into a virtual scroll view. FWIW, Copilot CLI has a slightly different issue, but is fundamentally the same, as they also use Ink (unfortunately). The good news is that they're working on using something like `ink-virtual-list`.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Bug Needs-Triage
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#23991
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?