[FEATURE] Maintain scroll position and keep the composer in view when typing while scrolled up

Open 💬 1 comment Opened Jun 12, 2026 by nkgardose

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

My normal workflow is asking Claude about architecture or implementation details, then asking follow up questions based on its answer. Those answers are usually really long. To ask a good follow up i scroll up to the part i care about.

There are really two problems here in my opinion:

  1. I want to keep reading the part of the answer i'm asking about. Right now the second i start typing, the view jumps back to the bottom and i lose the spot i was looking at.
  2. I want to see what i'm typing while i do it. The input needs to stay visible while i'm scrolled up, not be off screen at the bottom.

So i'm stuck doing both. Was just thinking that this might be a good feature to have.

Funny enough the Claude web client already does this. On Claude web client, i can scroll up to read part of a long answer and the input box stays put, and typing doesn't yank me back down. So this is really just bringing the CLI in line with what the web app already does.

Version and tech tools

Claude Code: v2.1.174, macOS, renderer /tui fullscreen (also happens on default), Terminal: iTerm2

What i've tried:

  1. TUI default renderer
  2. TUI fullscreen renderer
  3. autoScrollEnabled on and off (/config, Auto-scroll)

None of those let me keep the part of the answer i'm reading in view and see what i'm typing at the same time. In all of them the view snaps to the bottom once i start typing. The Auto-scroll toggle seems to only be about whether the view follows new streamed output, not about keeping my scroll position when i type.

Maybe i just missed something and there's already a way to do this. If so let me know and ignore this. But if not, a setting for it would be great.

Demo to problem

https://github.com/user-attachments/assets/cce560d0-5cd3-4ac9-b15c-9deba37df398

Proposed Solution

Add a config (something like preserveScrollPosition or stickyInput) that lets me keep my scroll position while typing and keeps the composer stuck in view. So i can scroll up, type a follow up, and still see both the part i'm reading and what i'm typing.

Maybe it's its own separate config, maybe it ties into the existing autoScrollEnabled, i don't know what makes more sense on your end. Either way default can stay as is and i just turn this on.

Alternative Solutions

What I do normally is just open a new panel of the same Claude session and scroll to that part of the conversation in panel 2 while i ask the question in panel 1

Completely solves the problem but it's more of my personal solution to it outside Claude Code

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case Example

Example scenario:

  1. I ask Claude to explain the architecture of a feature, like how auth and token refresh flow through the app.
  2. It gives a long answer, several screens worth.
  3. I scroll up to one specific section i want to ask about, say the part describing the refresh logic.
  4. I start typing a follow up question about that section.
  5. Today the view jumps to the bottom on the first keystroke, so i lose the section i was reading and can only see my own text once it's snapped down. I end up scrolling up to read, scrolling down to type, back and forth.
  6. With this feature the view stays on the refresh logic section, the input stays visible, and i type my follow up while reading the exact part i'm asking about.

Additional Context

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗