Skip to content

CLI: Scroll position jumps to top during long conversations #44087

New issue
New issue
Closed
Closed
CLI: Scroll position jumps to top during long conversations#44087
Labels
area:tuibugSomething isn't workingduplicateThis issue or pull request already existshas reproHas detailed reproduction stepsplatform:windowsIssue specifically occurs on Windows

Description

@lesliewangwyc-dev
lesliewangwyc-dev
opened on Apr 6, 2026

Description

During long CLI conversations, the scroll position unexpectedly jumps to the top of the conversation. This happens frequently and disrupts the workflow.

Reproduction

  1. Start a Claude Code CLI session
  2. Have a moderately long conversation (multiple exchanges with tool usage)
  3. Scroll up to review earlier content — scroll jumps to the top unexpectedly

Triggers

  • Mouse wheel scrolling — jumps to top
  • Dragging the scrollbar — jumps to top
  • During output generation — viewport jumps to top while Claude is streaming a response

Frequency

Happens frequently once the conversation becomes long enough.

Environment

  • Claude Code version: 2.1.92
  • OS: Windows 11 Home China (10.0.26200)
  • Shell: Git Bash (MSYS2)
  • Terminal: Windows Terminal (default)

Activity

  1. github-actions
    added
    bugSomething isn't working
    duplicateThis issue or pull request already exists
    platform:windowsIssue specifically occurs on Windows
    area:tui
    has reproHas detailed reproduction steps
    on Apr 6, 2026

  2. github-actions commented on Apr 6, 2026

    @github-actions
    github-actionsBot
    on Apr 6, 2026 – with GitHub Actions

    Found 3 possible duplicate issues:

    1. Scroll position jumps to top during streaming output on Windows Terminal #36621
    2. Windows: Scroll position jumps to old history when assistant outputs new text #43007
    3. Scrolling during streaming output jumps to top of session #35403

    This issue will be automatically closed as a duplicate in 3 days.

    • If your issue is a duplicate, please close it and 👍 the existing issue instead
    • To prevent auto-closure, add a comment or 👎 this comment

    🤖 Generated with Claude Code

  3. lesliewangwyc-dev commented on Apr 6, 2026

    @lesliewangwyc-dev
    lesliewangwyc-dev
    on Apr 6, 2026
    Author

    Closing as duplicate of #36621. Will add my additional observations there.

  4. lesliewangwyc-dev
    closed this as completedon Apr 6, 2026

  5. github-actions commented on Apr 15, 2026

    @github-actions
    github-actionsBot
    on Apr 15, 2026 – with GitHub Actions

    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.

  6. github-actions
    locked as resolved and limited conversation to collaborators on Apr 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:tuibugSomething isn't workingduplicateThis issue or pull request already existshas reproHas detailed reproduction stepsplatform:windowsIssue specifically occurs on Windows

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions