claude-code - 💡(How to fix) Fix [Feature Request] autoScrollEnabled should work in desktop app (non-fullscreen mode) [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#49183Fetched 2026-04-17 08:48:32
View on GitHub
Comments
0
Participants
1
Timeline
5
Reactions
0
Participants
Timeline (top)
labeled ×4cross-referenced ×1

Root Cause

  • #37627, #35512, #39652, #21631 (auto-scroll during generation - same root cause, different trigger)
RAW_BUFFERClick to expand / collapse

Problem

autoScrollEnabled: false in ~/.claude.json only works in fullscreen mode (/tui fullscreen). In the desktop app (non-fullscreen), submitting a message with Enter always scrolls to the bottom, ignoring the setting.

Use Case

I use a letter-anchor system (a-z, aa-zz) for referencing earlier parts of long conversations. When I'm scrolled up reading point "f)" and submit a reply referencing it, the view jumps to the bottom, losing my reading position. This breaks the workflow of navigating long, structured conversations.

Expected Behavior

autoScrollEnabled: false should preserve scroll position on message submit in ALL modes (desktop app, fullscreen, default TUI).

Current Behavior

  • Desktop app: setting ignored, always scrolls to bottom on submit
  • /tui fullscreen: setting works (the dq() fullscreen check gates the feature)
  • Submit handler calls l6() which checks X8().autoScrollEnabled, but only in fullscreen mode

Environment

  • Claude Code 2.1.110, Windows 11, desktop app
  • ~/.claude.json contains "autoScrollEnabled": false

Related Issues

  • #37627, #35512, #39652, #21631 (auto-scroll during generation - same root cause, different trigger)

extent analysis

TL;DR

The issue can be addressed by modifying the submit handler to respect the autoScrollEnabled setting in all modes, not just fullscreen.

Guidance

  • The current implementation only checks autoScrollEnabled in fullscreen mode, which is why the setting is ignored in the desktop app.
  • To fix this, the l6() function should be modified to check X8().autoScrollEnabled regardless of the mode.
  • The submit handler should be updated to preserve the scroll position when autoScrollEnabled is false.
  • Reviewing related issues (#37627, #35512, #39652, #21631) may provide additional context and insights into the root cause.

Example

No code snippet is provided as the issue does not contain sufficient information about the codebase.

Notes

The fix may require changes to the l6() function and the submit handler, which could have unintended consequences. Thorough testing should be performed to ensure the fix does not introduce new issues.

Recommendation

Apply a workaround by modifying the submit handler to respect the autoScrollEnabled setting in all modes, as this is a more targeted fix than upgrading to a potentially non-existent fixed version.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING