[FEATURE] **Feature Request: Disable Auto-Scroll in Claude Code Chat Panel**

Resolved 💬 2 comments Opened Mar 13, 2026 by metalbee66 Closed Mar 13, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

Summary
The Claude Code chat panel continuously auto-scrolls to the bottom as responses stream in. There is no way to lock or pause the scroll position while output is being generated.

Problem
When monitoring an active Claude session, the auto-scroll behaviour makes it impossible to read output as it streams. Any attempt to scroll up and read earlier output is immediately interrupted as the panel jumps back to the bottom when new content arrives. This creates a frustrating loop:

  1. Claude begins generating output
  2. User scrolls up to read earlier content
  3. New output arrives → panel auto-scrolls to bottom
  4. User loses their place and must scroll up again
  5. Repeat indefinitely

This is particularly painful for users who actively monitor Claude's progress in real time to catch errors or undesired behaviour early — which is often more efficient than waiting for a full run to complete before reviewing results.

Proposed Solution

Expected Behaviour
The chat panel should provide a way to lock or pause auto-scrolling, similar to the scroll-lock behaviour available in VS Code's integrated terminal. When scroll is locked, the panel stays at the user's current position regardless of new content arriving. A visual indicator (e.g. a "scroll to bottom" button) could appear to allow the user to jump back to the latest output when ready.

Suggested Solution
Add a scroll-lock toggle button to the Claude Code chat panel toolbar, consistent with the existing lock-scroll UX pattern in VS Code's terminal panel.

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

Interactive mode (TUI)

Use Case Example

A developer instructs Claude to refactor a large module across multiple files. Rather than waiting for the full task to complete, they monitor the chat panel in real time to catch issues early — such as Claude misunderstanding the intended logic, modifying the wrong file, or heading down a path that will require significant rework.
As Claude streams its output, the developer attempts to scroll up to re-read a previous step. The panel immediately snaps back to the bottom as new content arrives, forcing them to lose their place. This repeats every few seconds for the duration of the task.
By the time Claude finishes, several steps have already gone wrong that could have been caught and corrected mid-run — saving significant time and avoiding the need to undo completed work.

Additional Context

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗