Feature Request: Option to control auto-scroll behavior when submitting questions
Status Fixed / completed
Maintainer reply None cached
Activity 13 comments · opened Feb 11, 2026 · closed Aug 17, 2026
Feature Request
Current Behavior
When a user submits a question in Claude Code CLI, the terminal automatically scrolls to the bottom to show the assistant's response.
Desired Behavior
Add a configuration option to control scroll behavior, allowing users to:
- Keep the view at the position where they typed their question (instead of auto-scrolling to bottom)
- Or maintain current auto-scroll behavior (as default)
Use Case
When reviewing context or previous messages while waiting for a response, it would be helpful to stay at the current scroll position rather than being forced to the bottom. This would allow users to:
- Reference their question while reading the response
- Review earlier context without needing to scroll back up after each submission
Proposed Solution
Add a setting in Claude Code configuration (e.g., ~/.claude/config.json) like:
{
"autoScrollOnSubmit": true/false
}Environment
- Terminal: iTerm2
- OS: macOS (Darwin 23.5.0)
Thank you for considering this feature!
Showing cached comments. Read the full discussion on GitHub ↗
12 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
I second this motion!
+1, it's super confusing when we get long replies and have to scroll back up and try to find where we asked the question. The possible duplicates above have plenty of others with the same concerns, but they've been auto-closed.
Please add this feature. It is very hard to navigate long prompt windows currently.
this would be a big UX win, especially for multi-turn sessions where you're referencing earlier context. Even a simple keybinding to toggle auto-scroll on/off during generation would help.
Yeah even a setting to "scroll to last input" button/keybinding at this point.
It is extremely annoying! PLEASE fix it and do not close the issue as "not planned"!
+1, though I want to clarify a specific sub-case that I think is slightly different from the original report and worth calling out:
The problem I hit: I scroll up during an active run to read earlier output (e.g., a previous tool result or a step Claude already completed). The moment new output arrives — even a single new line — the viewport is forcibly snapped back to the bottom, making it impossible to read anything mid-stream.
This is distinct from the submit-time scroll described above. The issue isn't just "don't scroll when I hit Enter" — it's "if I have manually scrolled up, respect my scroll position while output continues to stream."
The expected behavior is standard in most terminal pagers and multiplexers: once the user scrolls up, the viewport stays pinned at that position while the buffer continues to grow below. A small "↓ new output" indicator at the bottom would be sufficient to signal that work is still in progress.
A
disableAutoScroll: truesetting insettings.jsonthat implements this "respect manual scroll position" behavior would fully address this.+1 — this is a real pain point when reviewing long output (articles, code, search results). The standard behavior in every terminal/chat app is: auto-scroll only when the user is already at the bottom. If they've scrolled up, respect that.
please fix it. it's unbearable
Much needed, thanks!:)
This is extremely annoying...