[BUG] Uninterruptible "high speed scrolling" of Claude Code terminal in IntelJIdea

yup noticing the same thing . Sometimes it get's stuck when scrolling, especially upwards.

Running Claude 4 in Claude Code through WSL in Windows 11. Worked great all day, but then started endlessly yoyo scrolling for the past 30 minutes. Only thing that would stop is was closing the window, so not an IDE problem, but a Claude Code issue.

Same problem. I was hoping to find some setting to clear buffer or stop the scrolling.

same problem, claude code scrolling super fast strangely

I'd be glad to even just figure out what triggers this (if anything) so I could avoid it.

I've faced this as well. At least on mac, if I press esc a couple of times, it will get out of this madness 😄 And then i just tell it to "carry on" and it will usually resume

Same problem only thing I can do is esc and say continue, sometimes I have to control-c or control-z to break it and reopen. This is on Ubuntu LTS

https://github.com/user-attachments/assets/35f67121-65fc-4fe8-a7b8-7f1f14b6a606

Same problem here, it's really annoying. Running it on a Mac.

Running into the same problem every few prompts - Mac - Cursor terminal

Same issue here, VSCode, WSL on Windows

I've been having this bug since forever.

Best way to reproduce:

• Get over 50% context
• Spawn 9 parallel tasks
• Each of them should ask for modification approvals and commands approvals from time to time

The whole terminal will break, in fact it will crash most terminals completely if not stopped in time.

https://github.com/user-attachments/assets/08aae3ec-a035-4f7b-8eac-e60645de0c76

I am experiencing this bug as well. I am running 10 sub agents, modification approvals as well, very similar to OpenSource03

I am using windsurf, claude code is usually buggy on any terminal I am on but it has never been this bad.

It's completely unusable, I just bought the max plan a couple of days ago and I am considering asking for a refund. What's the point of buying claude max if it is so clearly not supportive of my OS or any of the software I use?? Ridiculous.

https://github.com/user-attachments/assets/08aae3ec-a035-4f7b-8eac-e60645de0c76 I am experiencing this bug as well. I am running 10 sub agents, modification approvals as well, very similar to OpenSource03 I am using windsurf, claude code is usually buggy on any terminal I am on but it has never been this bad. It's completely unusable, I just bought the max plan a couple of days ago and I am considering asking for a refund. What's the point of buying claude max if it is so clearly not supportive of my OS or any of the software I use?? Ridiculous.

Yours is quite slow, mine does enter hyper speed from time to time 😂

> https://github.com/user-attachments/assets/08aae3ec-a035-4f7b-8eac-e60645de0c76 > > I am experiencing this bug as well. I am running 10 sub agents, modification approvals as well, very similar to OpenSource03 > > I am using windsurf, claude code is usually buggy on any terminal I am on but it has never been this bad. > > It's completely unusable, I just bought the max plan a couple of days ago and I am considering asking for a refund. What's the point of buying claude max if it is so clearly not supportive of my OS or any of the software I use?? Ridiculous. Yours is quite slow, mine does enter hyper speed from time to time 😂

I know exactly what you mean :( the only reason mine was slow was because I wasn't running any tasks, but the hyper speed is definitely a problem lmao

WINDOWS USERS: as far as I can tell, one of the big reasons this terminal error occurs has to do with having too many subagents deployed. after reducing the amount of subagents from 7-10 to 3-5 at any given moment, the terminal is far less glitchy.

WINDOWS USERS: as far as I can tell, one of the big reasons this terminal error occurs has to do with having too many subagents deployed. after reducing the amount of subagents from 7-10 to 3-5 at any given moment, the terminal is far less glitchy.

It may still very well happen with no agents at all sometimes, much more rare tho.

I'm experiencing the same issue on macOS with every terminal I've tried.

It's time to try the other CLI tools. No one at Anthropic seems to care about this tool. 😔 On Jun 30, 2025, at 5:11 PM, Sol Midnight @.***> wrote:solmidnight left a comment (anthropics/claude-code#1422)
I'm experiencing the same issue on macOS with every terminal I've tried.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

I have to get my moneys worth. I paid 200 dollars. You think I should chargeback?

Why isn't anyone at Anthropic responding to this?

I'm consistently getting this error as well - non-stop terminal scrolling and nothing apparent to stop sometimes without ending the terminal session. Anecdotally, it seems to occur after I have pasted text at some point in the terminal, but will need to do more testing to confirm.

Paste seems to be one way to trigger, the longer the paste the greater the thrashing. Seems like each character in the buffer jumps it to the top and it has to scroll back. So you have to sit there for several minutes or hit CTRL-C and lose work. It's a P0 bug and apparently no one at anthropic either cares or is clever enough to fix it. -Poke- -come on team, do better-Sent from a mobile device.On Jul 11, 2025, at 1:20 PM, FLpilot @.***> wrote:FLpilot left a comment (anthropics/claude-code#1422)
I'm consistently getting this error as well - non-stop terminal scrolling and nothing apparent to stop sometimes without ending the terminal session. Anecdotally, it seems to occur after I have pasted text in the terminal, but will need to do more testing to confirm.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

Happens to me too, the longer the chat window goes, the more likely it is to happen. And yes, you can't recover it. So I lose all the latest prompts, so I can't even easily restart a new window. I have to start from scratch totally, which is sad

This affects me too, but I find the feature disorienting even when it's working as it's supposed to. Does it look terrible if you just let the terminal handle scrolling content on its own? I'm using a modern GPU-powered terminal (Ghostty); I'd be shocked if it didn't do a far better, smoother job than a Node.js app running inside it.

This happens in Visual Studio 2022 17.14.9 as well

I have the same in Cursor.

same thing in jetbrains ides.

seeing this when running npm unit tests in subtasks, when the tests produce significant error/warning logs.

if i let it continue to run, eventually the tests complete and the issue stops.

Same here, apparently this is going on for months now. Happens when the context grows beyond a certain length. Might have something to do with copy-pasting in the prompt.

@bcherny, this is negative vibe for your otherwise brilliant app. Can nothing be done?

Note that this happens on wsl and on another server with ubuntu 24.04

I run into this issue frequently in WSL but I have found a workaround there, which is:
ctrl-c ctrl-c to exit claude
clear to clear terminal scrollback (note NOT claude's /clear)
then claude --resume to pick up where you left off, but without the crazy scrolling (for a little while anyway)

Same issue here, all the time.

Win 11, wsl in vscode.

Trigger points seem to be pasting or resizing the window/tab. not consistently though.

It usually stops on its own eventually.

I run into this issue constantly. It does stop on its own eventually, but it's such a time consuming issue. Anytime it starts happening, it gets worse and worse and takes more and more time for it to stop scrolling. PLEASE find the root cause anthropic 😬

This issue happened to me every day even everytime. It has been 2 months passed could you guys use your claude code to fix it?

+1, windows, wsl problem with a longer conversation and pasting text, conversation starts to scroll like crazy

Same in VSCode on macOS. Especially a problem when pasting, starting many sub-agents, etc.

same here with JetBrains terminals in every IDE on Mac. It drives me crazy

+1, 2 months later

You would think with the kind of revenue they're in that at least someone would look into it. Do you think watching that revenue fall off a cliff might do it? GPT-5 FTW. On Aug 7, 2025, at 11:35 PM, Paul @.***> wrote:pde-rent left a comment (anthropics/claude-code#1422)
+1, 2 months later

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

Cursor is giving away free use of GPT-5 in an apparent bid for the developer market. Currently testing. Claude Code's lifespan is looking to be brief, at this rate. On Aug 8, 2025, at 10:24 AM, Michael @.***> wrote:mikeparisstuff left a comment (anthropics/claude-code#1422)
I absolutely love claude code but its hard to overstate how distracting and broken this behavior is. Sharing here because I don't want to churn as a customer, but this behavior is likely to be the no. 1 reason why I would. Please prioritize and fix this as it ruins all the other great work your team does.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

I would like to point out that, as a user who has a visual processing issue, this bug makes me want to vomit literally. Claude Code is so fun when it works, but for accessibility and convenience reasons alike...this bug should really get fixed soon, please! 🙏🏻

Windows 11, VS Code + wsl

Nathaniel- they (Anthropic) appear not to care, not assigning anyone to look at the bug, we just have to continue foraging for new tools and let Amodei wonder why his graph changed shape 📈 📉 Sent from a mobile device.On Aug 9, 2025, at 3:37 PM, Nathanial P. Howard @.***> wrote:OptimusPi left a comment (anthropics/claude-code#1422)
I would like to point out that, as a user who has a visual processing issue, this bug makes me want to vomit literally. Claude Code is so fun when it works, but for accessibility and convenience reasons alike...this bug should really get fixed soon, please! 🙏🏻
Windows 11, VS Code + wsl

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

Just a hunch: I think this has something to do with the CTRL+R expansion getting activated when it shouldn't, or interfering with scrolling in weird circumstances. Whatever it is, it's driving me nuts.

A few things I tried to see if it's some sort of incompatibility:

• I removed ohmyzsh
• I removed powershell10k

Removing those didn't fix it. It still happens. But it's admittedly faster just because I think there was overhead with those two things installed.

I'm still using tmux and starship prompt though. Just trying to add as much info to help with debugging...

@walt93

You would think with the kind of revenue they're in that at least someone would look into it.

There are currently over 3,000 open issues in this repo.

I think this is better in the latest versions, I'm on 1.0.71, but this was mentioned in the release notes for 1.0.70:

Version 1.0.70: • Performance: Optimized message rendering for better performance with large contexts

When resizing, it now rapidly reflows the text and doesn't get stuck anymore, it seems. This is inside Visual Studio Code and Cursor.

One of the situations that would cause this is pasting in large amounts of text, and I just pasted in over 3,800 lines with no issue.

@walt93 > You would think with the kind of revenue they're in that at least someone would look into it. There are currently over 3,000 open issues in this repo.

Are they as active as this one? Didn't think so. There should be priority... Also the sheer number of issues indicates that they are not putting enough care into it.

The fact that this has still not been resolved and closed is funny. How can anyone take you guys seriously at this point? At least ask Claude Code to suggest a fix for itself 🤣

For the recent commenters @koin-marian @OpenSource03 have you tested on 1.0.71?

I used to get this a couple of times a day, and I haven't seen it in a few days, which is a huge improvement!

Update: it sort of happens it seems, but clears up after 15-20 seconds. Haven't got entirely stuck, yet.

Yeah, it never got completely stuck for me on Mac OS, it stops acting crazy after 15-20 seconds, but still annoying.

Well, it just happened to me. Completely stuck in an infinite loop.

Also the same bug. in macOs 15.5, cursor terminal.

Same issue here. Very annoying

Annoying is the wrong word. It's prohibitive.

I suspect this has something to do with ctrl+r to expand results. I don't know... just a shot in the dark. I hope someone/thing at anthropic is working on this.

Same issue and it's very annoying.

Same here, that is is extremely annoying and can only be fixed by killing the terminal. CC inside latest Cursor on Win10.

This has now made it impossible for me to properly configure tool access for sub-agents, because the second I try to use the arrow keys to pick a specific tool during the interactive agent setup, this scroll bug happens.

This is getting extremely frustrating. No other terminal application I've used has ever done anything like this.

I mean why is there no focus on it? No work around like some settings in iterm 2?
I mean it doesn't seem to be a new bug?
2 Months ago
https://www.reddit.com/r/ClaudeAI/comments/1ll8bu1/has_anyone_figured_out_how_to_stop_the_window/
1 Month ago
https://www.reddit.com/r/ClaudeAI/comments/1lwc4nz/claude_code_going_completely_bonkers/

I mean it doesnt seem to be a such complex bug compared to what Claude it self is?

I cant work on my android tablet terminal because of this fucking anooying scrolling history terminal content. Fuckkkk ittt

A potential (yet ridiculous) workaround is to use a custom GUI overlay on top of Claude Code like Claudia: https://claudiacode.com/

I can confirm no scroll insanity with that, but of course that's not an ideal solution...

I've used claudia and love the idea of it, but it isn't production ready imo. Ironically, I found that it has its own scrolling issue where it just doesn't scroll and I have to constantly manually scroll.

The best part of this bug is that it'll eventually crash VScode if the terminal is inside of the UI (easier diff tracking for human meatsacks)

_I was deeply curious why this bug has been around for so long so I asked Claude what was wrong with Claude and this is probably why:_

Claude Code Terminal Scrolling Bug: Deep Technical Analysis

Executive Summary

The "infinite scrolling" bug in Claude Code is actually a cluster of related issues stemming from fundamental problems in buffer management, terminal state synchronization, and context handling. The bug manifests across all platforms but with varying symptoms.

Root Cause Analysis

1. Internal Buffer Management Conflict

Claude Code maintains its own scrollback buffer independent of the terminal emulator's buffer. This creates a dual-buffer problem:

• Claude's Buffer: Stores conversation context and command history
• Terminal's Buffer: Manages actual display output
• Synchronization Failure: These buffers desynchronize when large outputs exceed threshold limits

2. Context Compaction Trigger Points

The scrolling often starts when:

• Context usage exceeds ~50% (around 100K tokens)
• Large error outputs (>28K characters) are displayed
• Multiple newlines or ANSI escape sequences are processed
• Jest/test frameworks output formatted error messages

3. Terminal State Machine Corruption

Normal State → Large Output → Buffer Overflow → State Corruption → Infinite Redraw Loop
                                                        ↑                    ↓
                                                        ←────────────────────

Specific Bug Patterns Identified

Pattern A: Rapid Scrolling (Issues #1422, #3648)

• Trigger: High context usage + large output
• Behavior: GPU-accelerated scrolling at uncontrollable speed
• Technical Cause: Render loop attempting to display entire buffer repeatedly
• Why Ctrl-C Fails: Input handler bypassed during render loop

Pattern B: Yo-Yo Scrolling (Issues #367, #826)

• Trigger: Long terminal history + new output
• Behavior: Scrolls to top, then bottom, repeatedly
• Technical Cause: Conflicting scroll position updates between Claude and terminal
• Platform: Most common on macOS/iTerm2

Pattern C: Infinite Compaction Loop (Issue #6004)

• Trigger: Context window limit approached
• Behavior: Repeatedly reads files, compacts, loses state, re-reads
• Technical Cause: State loss during compaction forces re-initialization
• Impact: Makes complex tasks impossible

Pattern D: Cursor Runaway (Issue #832)

• Trigger: Large test output in WSL2
• Behavior: Cursor scrolls over text, entire context scrolls per character
• Technical Cause: Character-by-character rendering with full buffer refresh
• Environment: WSL2-specific terminal translation issues

Technical Deep Dive

Buffer Architecture Flaw

// Hypothetical problematic code structure
class TerminalRenderer {
  private internalBuffer: string[] = [];
  private renderQueue: RenderTask[] = [];
  
  async processLargeOutput(output: string) {
    // Problem 1: No chunking
    this.internalBuffer.push(output);
    
    // Problem 2: No rate limiting
    while (this.renderQueue.length > 0) {
      await this.render(); // Can create infinite loop
    }
    
    // Problem 3: No escape mechanism
    // Ctrl-C doesn't interrupt this loop
  }
}

Missing Circuit Breakers

The code lacks:

1. Render Rate Limiting: No max renders/second
2. Output Chunking: Large outputs not paginated
3. Escape Sequences: No emergency stop mechanism
4. Memory Pressure Detection: No context limit warnings

Terminal Emulator Interactions

Different terminals handle the bug differently:

• iTerm2: Shows yo-yo scrolling pattern
• WSL2/Windows Terminal: Cursor runaway and character-by-character scrolling
• VSCode Terminal: Complete freeze requiring restart
• IntelliJ Terminal: High-speed continuous scrolling

Why Traditional Interrupts Fail

Signal Handler Bypass

User Input (Ctrl-C) → Terminal → Claude Code
                         ↓
                    [Render Loop Active]
                         ↓
                    Signal Ignored

The render loop operates at a lower level than the signal handler, preventing interrupts from being processed.

Terminal Raw Mode Issues

Claude Code likely uses raw mode for terminal control, which:

• Disables normal signal processing
• Requires explicit signal handling
• Can ignore interrupts during tight loops

Recommended Fixes

Immediate Patches

1. Render Throttling

const MAX_RENDERS_PER_SECOND = 30;
let lastRenderTime = 0;

function throttledRender() {
  const now = Date.now();
  if (now - lastRenderTime < 1000 / MAX_RENDERS_PER_SECOND) {
    return;
  }
  lastRenderTime = now;
  performRender();
}

1. Output Chunking

function chunkOutput(output: string, maxChunkSize = 1000) {
  const chunks = [];
  for (let i = 0; i < output.length; i += maxChunkSize) {
    chunks.push(output.slice(i, i + maxChunkSize));
  }
  return chunks;
}

1. Emergency Stop Mechanism

let emergencyStop = false;
process.on('SIGINT', () => {
  emergencyStop = true;
  process.exit(1);
});

function renderLoop() {
  if (emergencyStop) return;
  // ... rendering logic
}

Long-term Architecture Changes

1. Decouple Buffer Management

• Separate display buffer from context buffer
• Implement virtual scrolling for large outputs
• Use terminal's native scrollback when possible

1. Progressive Rendering

• Stream outputs in chunks
• Implement pagination for large responses
• Add "Show More" functionality

1. Context Management Overhaul

• Preserve task state during compaction
• Implement incremental compaction
• Add context usage warnings

User Workarounds (Until Fixed)

Prevention

1. Clear context regularly: Use /clear or start new sessions
2. Limit output size: Redirect large outputs to files
3. Monitor context usage: Stay below 50% when possible

Recovery Methods

1. Process Termination (Most Reliable)

``bash
# Find Claude Code process
ps aux | grep claude
# Kill the process
kill -9 <PID>
``

1. Terminal Reset

• Close terminal tab completely
• For iTerm2: Cmd+K to clear buffer
• For VSCode: Kill terminal and create new

1. System Monitor

• Use Activity Monitor (macOS) or Task Manager (Windows)
• Force quit Node.js processes

Impact Assessment

Severity: CRITICAL

• Data Loss Risk: Medium (unsaved work may be lost)
• Productivity Impact: High (requires restart, loses context)
• User Experience: Very Poor (unresponsive, requires force quit)
• Frequency: Increases with session length and complexity

Affected Workflows

• Long coding sessions
• Test-driven development (large test outputs)
• Complex multi-file refactoring
• Any task approaching context limits

Conclusion

The scrolling bug is a symptom of deeper architectural issues in Claude Code's terminal handling and buffer management. The immediate fix requires implementing circuit breakers and rate limiting, while the long-term solution demands a fundamental redesign of the buffer architecture and context management system.

The cross-platform nature and variety of symptoms indicate this is not a simple bug but a systemic issue requiring comprehensive refactoring of the terminal interaction layer.

---
Analysis based on issues #367, #826, #832, #1413, #1422, #2118, #3648, #4647, #4851, #6004

I believe if Claude was capable of fixing this bug, it would be long since closed. My theory (especially after watching a podcast with Anthropics co founder - he presents as seriously not capable of that role 🤯) is that no one on Anthropic staff is able to fix this & they are simply waiting for a stronger model. (Prove me wrong, Anthropic engineers - the dare is on you!)On Aug 20, 2025, at 7:12 AM, Justin Shearer @.***> wrote:justin-dakota left a comment (anthropics/claude-code#1422)
I was deeply curious why this bug has been around for so long so I asked Claude what was wrong with Claude and this is probably why
Claude Code Terminal Scrolling Bug: Deep Technical Analysis
Executive Summary
The "infinite scrolling" bug in Claude Code is actually a cluster of related issues stemming from fundamental problems in buffer management, terminal state synchronization, and context handling. The bug manifests across all platforms but with varying symptoms.
Root Cause Analysis

1. Internal Buffer Management Conflict

Claude Code maintains its own scrollback buffer independent of the terminal emulator's buffer. This creates a dual-buffer problem:

Claude's Buffer: Stores conversation context and command history
Terminal's Buffer: Manages actual display output
Synchronization Failure: These buffers desynchronize when large outputs exceed threshold limits

1. Context Compaction Trigger Points

The scrolling often starts when:

Context usage exceeds ~50% (around 100K tokens)
Large error outputs (>28K characters) are displayed
Multiple newlines or ANSI escape sequences are processed
Jest/test frameworks output formatted error messages

1. Terminal State Machine Corruption

Normal State → Large Output → Buffer Overflow → State Corruption → Infinite Redraw Loop
↑ ↓
←────────────────────

Specific Bug Patterns Identified
Pattern A: Rapid Scrolling (Issues #1422, #3648)

Trigger: High context usage + large output
Behavior: GPU-accelerated scrolling at uncontrollable speed
Technical Cause: Render loop attempting to display entire buffer repeatedly
Why Ctrl-C Fails: Input handler bypassed during render loop

Pattern B: Yo-Yo Scrolling (Issues #367, #826)

Trigger: Long terminal history + new output
Behavior: Scrolls to top, then bottom, repeatedly
Technical Cause: Conflicting scroll position updates between Claude and terminal
Platform: Most common on macOS/iTerm2

Pattern C: Infinite Compaction Loop (Issue #6004)

Trigger: Context window limit approached
Behavior: Repeatedly reads files, compacts, loses state, re-reads
Technical Cause: State loss during compaction forces re-initialization
Impact: Makes complex tasks impossible

Pattern D: Cursor Runaway (Issue #832)

Trigger: Large test output in WSL2
Behavior: Cursor scrolls over text, entire context scrolls per character
Technical Cause: Character-by-character rendering with full buffer refresh
Environment: WSL2-specific terminal translation issues

Technical Deep Dive
Buffer Architecture Flaw
// Hypothetical problematic code structure
class TerminalRenderer {
private internalBuffer: string[] = [];
private renderQueue: RenderTask[] = [];

async processLargeOutput(output: string) {
// Problem 1: No chunking
this.internalBuffer.push(output);

// Problem 2: No rate limiting
while (this.renderQueue.length > 0) {
await this.render(); // Can create infinite loop
}

// Problem 3: No escape mechanism
// Ctrl-C doesn't interrupt this loop
}
}
Missing Circuit Breakers
The code lacks:

Render Rate Limiting: No max renders/second
Output Chunking: Large outputs not paginated
Escape Sequences: No emergency stop mechanism
Memory Pressure Detection: No context limit warnings

Terminal Emulator Interactions
Different terminals handle the bug differently:

iTerm2: Shows yo-yo scrolling pattern
WSL2/Windows Terminal: Cursor runaway and character-by-character scrolling
VSCode Terminal: Complete freeze requiring restart
IntelliJ Terminal: High-speed continuous scrolling

Why Traditional Interrupts Fail
Signal Handler Bypass
User Input (Ctrl-C) → Terminal → Claude Code
↓
[Render Loop Active]
↓
Signal Ignored

The render loop operates at a lower level than the signal handler, preventing interrupts from being processed.
Terminal Raw Mode Issues
Claude Code likely uses raw mode for terminal control, which:

Disables normal signal processing
Requires explicit signal handling
Can ignore interrupts during tight loops

Recommended Fixes
Immediate Patches

Render Throttling

const MAX_RENDERS_PER_SECOND = 30;
let lastRenderTime = 0;

function throttledRender() {
const now = Date.now();
if (now - lastRenderTime < 1000 / MAX_RENDERS_PER_SECOND) {
return;
}
lastRenderTime = now;
performRender();
}

Output Chunking

function chunkOutput(output: string, maxChunkSize = 1000) {
const chunks = [];
for (let i = 0; i < output.length; i += maxChunkSize) {
chunks.push(output.slice(i, i + maxChunkSize));
}
return chunks;
}

Emergency Stop Mechanism

let emergencyStop = false;
process.on('SIGINT', () => {
emergencyStop = true;
process.exit(1);
});

function renderLoop() {
if (emergencyStop) return;
// ... rendering logic
}
Long-term Architecture Changes

Decouple Buffer Management

Separate display buffer from context buffer
Implement virtual scrolling for large outputs
Use terminal's native scrollback when possible

Progressive Rendering

Stream outputs in chunks
Implement pagination for large responses
Add "Show More" functionality

Context Management Overhaul

Preserve task state during compaction
Implement incremental compaction
Add context usage warnings

User Workarounds (Until Fixed)
Prevention

Clear context regularly: Use /clear or start new sessions
Limit output size: Redirect large outputs to files
Monitor context usage: Stay below 50% when possible

Recovery Methods

Process Termination (Most Reliable)

Find Claude Code process

ps aux | grep claude

Kill the process

kill -9 <PID>

Terminal Reset

Close terminal tab completely
For iTerm2: Cmd+K to clear buffer
For VSCode: Kill terminal and create new

System Monitor

Use Activity Monitor (macOS) or Task Manager (Windows)
Force quit Node.js processes

Impact Assessment
Severity: CRITICAL

Data Loss Risk: Medium (unsaved work may be lost)
Productivity Impact: High (requires restart, loses context)
User Experience: Very Poor (unresponsive, requires force quit)
Frequency: Increases with session length and complexity

Affected Workflows

Long coding sessions
Test-driven development (large test outputs)
Complex multi-file refactoring
Any task approaching context limits

Conclusion
The scrolling bug is a symptom of deeper architectural issues in Claude Code's terminal handling and buffer management. The immediate fix requires implementing circuit breakers and rate limiting, while the long-term solution demands a fundamental redesign of the buffer architecture and context management system.
The cross-platform nature and variety of symptoms indicate this is not a simple bug but a systemic issue requiring comprehensive refactoring of the terminal interaction layer.

Analysis based on issues #367, #826, #832, #1413, #1422, #2118, #3648, #4647, #4851, #6004

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

Absolutely agreed @walt93, Claude can't just solve the issue. My take away from Claude's assessment was that it's a complex set of problems that is not easy to fix, hence why it's taken them so long to address it. Yeah there _might_ be some hacky quick wins but it still won't fix the overall underlying issue.

I cannot speak to its quality as I've only just started using it, but OpenCode is iterating and improving extremely quickly and allows Oauth against your Claude Pro/Max Subscription. It may be worth trying: https://opencode.ai/

No terminal scroll bug yet, about 2 hours in to using it.

bump

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.