Cursor scroll chat history to unpredictable place when switching between chats

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When I have few chats ans switching between them, the cursor scrolls history to unpredictable place thus I am forced to spend a lot of time to find the place where I left. This is very annoying.

Steps to Reproduce

  1. Open chat 1 ask few questions
  2. Open chat 2 ask few questions
  3. Scroll a bit up at chat two
  4. switch to chat 1
  5. switch to chat 2

Expected Behavior

After switching back to chat 2 I expect to see the place where I left, but I see that cursor jumps to some other unpredictable places.

Operating System

MacOS

Version Information

Version: 2.7.0-pre.45.patch.0
VSCode Version: 1.105.1
Commit: 447839e5318c8d58f2447eeeca8f440ae1b72d09
Date: 2026-03-10T05:34:36.213Z
Build Type: Nightly
Release Track: Default
Electron: 39.6.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.3.0

Does this stop you from using Cursor

Yes - Cursor is unusable

Another issue cursor jump also unpredictably when I am scrolling the current chat history.
The current text in window should stay at the same place.
Why this happens; when I scroll chat by dragging scrollbar Cursor loads new history, this event triggers scrollbar repositioning, but because I am dragging it at this moment the position becomes wrong. After scroll bar repositioning by Xpixels the mouse should be programatically repositioned by this number of Xpixels. Thus will allow to continue scrolling the current visible window without jumping to somewhere else.

Hey, thanks for the report. This is a known issue. Scroll position isn’t saved when switching between chats. The team is aware, and your report helps with prioritization.

The main thread for this bug is here: Chat view scroll position resets when switching between conversations

About the second note on jumping while scrolling through a long history when virtualization loads more content, that’s a related issue and it’s being tracked too.

There’s no timeline for a fix yet, but the bug is logged. Let me know if you notice anything else.

1 Like

This should have high priority, because this stops from working normally. This issues borrow extra time from users.

1 Like

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.