[BUG] VS Code Extension — Severe Regressions since v2.0.34

Status Closed — not planned
Maintainer reply ✓ Yes — blois
Activity 15 comments · opened Nov 12, 2025 · closed Feb 14, 2026
💡 Likely answer: A maintainer (blois, collaborator) responded on this thread — see the highlighted reply below.

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?

Since extension version 2.0.35+, Claude Agent interactions have become significantly slower and the extension introduces UI regressions in the panel/log view: heavy lags, broken manual scrolling, and an aggressive auto-scroll that constantly yanks the view to the bottom. When the session “runs out of context,” the context consolidationstalls for 10+ minutes with little/no progress feedback, blocking further work. These issues cause major productivity loss.

---

Issues & Impact

1) Severe lag / UI jank during agent runs

  • Observed: Large latency and stutters while Claude is generating; editor and extension panel become sluggish (typing, panel resizing, switching tabs).
  • Impact: Editor responsiveness degrades; cumulative delays, frequent need to pause until the agent finishes.

2) Broken manual scrolling in the Agent/Chat panel

  • Observed: While agent is streaming, manual scroll cannot stay at prior position; view is force-snapped back to the latest chunk (“current index”).
  • Regression: Prior to 2.0.35, we could scroll up to inspect reasoning steps and then jump back down to live output.
  • Impact: Impossible to review intermediate steps or copy earlier content while agent is still working; interrupts interactive workflows.

3) Aggressive auto-scroll with no reliable override

  • Observed: Auto-scroll constantly re-enables/overrides user scrolling intent during streaming.
  • Impact: Disastrous UX: the view keeps jumping, causing lost selection, mis-clicks, and wasted time.

4) Excessive delay on “context consolidation” when out of context

  • Observed: When the session reaches token limits, the extension enters a “consolidation” phase that may stall ≥ 10 minutes before resuming.

Overall severity: High (Daily productivity regression, repeated blocking).

---

Notes

  • Behavior was correct before v2.0.35: manual scroll remained stable during streaming, and overall responsiveness was acceptable.
  • The current behavior appears to be a clear regression in scroll handling + rendering + consolidation performance.

What Should Happen?

  • Smooth editor responsiveness during streaming.
  • User-controlled scroll that stays where the user left it until they opt back into live auto-scroll.
  • Context rollover within seconds, or at least with transparent progress, cancellability, and the ability to continue working.

Error Messages/Logs

Steps to Reproduce

  1. Open a medium/large project (TypeScript/Node monorepo works reliably).
  2. Trigger a Claude Agent task that streams a long response (e.g., multi-file refactor with reasoning).
  3. While streaming:
  • Attempt to scroll up in the chat/agent panel to review earlier reasoning.
  • Observe forced auto-scroll back to bottom; selection is lost.
  1. Continue sending follow-up prompts until the session hits context limits.
  2. Observe context consolidation takes several minutes with little/no progress feedback.

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2.0.34

Claude Code Version

2.0.37

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

15 Comments

github-actions[bot] · 9 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/11092
  2. https://github.com/anthropics/claude-code/issues/9557
  3. https://github.com/anthropics/claude-code/issues/10881

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

akshaycj · 9 months ago

+1

neotradingbot · 9 months ago

I've got the exact same issue!

blois collaborator · 9 months ago

Thanks for the feedback. Improvements to 1, 2 & 3 should be arriving very shortly (in the next version). Improvements to #4 are in progress but not completed yet.

izwombat · 9 months ago

+1 great job detailing out each issue i simply couldn't find the words for. 💃

OpenSource03 · 9 months ago
Thanks for the feedback. Improvements to 1, 2 & 3 should be arriving very shortly (in the next version). Improvements to #4 are in progress but not completed yet.

@blois
Just to note, the latest version (2.0.42) fixed scroll issues in claude code itself, but the rest of IDE, while claude is generating, is having frozen or flickering scroll bars, not allowing for scroll actions anywhere but in claude code.

The last version when whole Cursor scroll UI was not flickering and being frozen for me was 2.0.35.

neotradingbot · 9 months ago

I've rolled back to version 2.0.35 as well and can confirm that none of the above issues are there in that version.. will wait for the new update to stabilize before updating again.

duskosusa · 9 months ago

Same here, 2.0.35 is the last one that doesn't flicker

OpenSource03 · 9 months ago

Still seeing issues even on latest version as of now...

blackholegalaxy · 9 months ago

Still flickering issues accross IDE... It's REALLY boring and prevent any parallel task

damian-dp · 8 months ago

Yep still getting this flickering and focus switching breaking scroll when claude code extension is working.

Extension version 2.0.58

Any progress on a fix for this?

lukasz-zimnoch · 8 months ago

+1 as it still occurs for 2.0.75. Any plans to fix this in the near future?

github-actions[bot] · 7 months ago

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

github-actions[bot] · 6 months ago

Closing for now — inactive for too long. Please open a new issue if this is still relevant.

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