[FEATURE] Sticky/Fixed Input Mode - Keep input visible while scrolling output
Resolved 💬 18 comments Opened Dec 10, 2025 by Kostya950 Closed May 12, 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
When Claude outputs long content (like file contents, logs, or explanations),
the input field scrolls out of view. Users must scroll down to type,
then scroll up to review output, creating friction in the workflow.
Proposed Solution
A "sticky input" or "split view" mode where:
- Input field stays fixed at the bottom of the terminal
- Output/conversation area scrolls independently above it
- Similar to chat apps or VS Code's integrated terminal sticky-scroll
Alternative Solutions
- Using tmux splits (works but adds complexity)
- IDE integration (not always available)
Priority
High - Significant impact on productivity
Feature Category
CLI commands and flags
Use Case Example
When reviewing/editing files through Claude Code:
- Ask Claude to show a file
- Want to scroll through the output to review it
- Need to type follow-up instructions
- Currently: must scroll down to find input, losing context
Additional Context
This would significantly improve UX for iterative file editing workflows.
18 Comments
Found 1 possible duplicate issue:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
I agree. I mentioned to @ThariqS too. I use Claude web/desktop mainly so am used to that behavior
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.
Yes, this is.
Yes, please, it's so painful having to type, look, scroll, type, look, scroll...
+1 on this. I'm using Claude Code on WSL (WezTerm) and experience this exact pain daily.
My workflow friction:
This back-and-forth scrolling is the single biggest UX friction point for me. A sticky/pinned input bar at the bottom — similar to how every modern chat app works — would be a huge productivity boost.
Environment: Claude Code v2.1.45, WSL2 Ubuntu 24.04, WezTerm
+1. It's most effective to batch your replies to Claude since the turn-based LLM is slow to respond. But when composing a multi-point reply, I'm constantly scrolling up to re-read parts of Claude's output, then back down to add another line to my response. The input field disappearing off-screen makes this painful.
A sticky input at the bottom with independently scrollable output above would let me reference Claude's response while composing my reply — the same way any chat app works. This is the single biggest UX friction point for me.
+1 on it
+1 I also would love this feature, as I scroll in the answers a lot when needing to respond. I then can't type while reading the part I want to answer. Looked online and no solutions, except hardcoding a terminal command.
Please have a look for window-scrollers around the world ;-)
Watching on this thread too. It's a pain.
+1
+1
+1 on this thread
POTENTIAL FIX for some: (This fixed my issue)
Run Claude code with this environment variable
CLAUDE_CODE_NO_FLICKER=1If you are on Mac/Linux, you can add this as an
aliasto your~/.zshrcor~/.bashrc...Something like:
alias claude='CLAUDE_CODE_NO_FLICKER=1 claude'or
alias cc='CLAUDE_CODE_NO_FLICKER=1 claude'workss
/tui fullscreendoes the trickTo make it permanent add to your
claude/settings.json:/tui fullscreenthat was released in version2.1.110does the job, so this issue can be closed.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.