Cursor jump to selected prompt box field jumps to wrong position

[Benutzer4 (Info)]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I noticed an issue in a context window with a longer iterative process, although it can probably also be reproduced in a smaller context window. The functionality where it jumps back to a previous position is causing problems.

Specifically, if I have a long context window that I am currently working in within a chat window, and I scroll upward, the old context is repeatedly loaded from the history. That includes the individual chat windows where I, as the end user, entered new requirements.

I have noticed very often that when I scroll up to older states, there is a problem. What stood out most is the very first entry at the very top, and that is the primary issue. When I go all the way back to the top into the very first chat box history, where the original prompt was entered, and I click into it with the mouse, I cannot get into it because the IDE jumps back down again.

So something is wrong with the mechanism that jumps back to a certain place in the chat window when I click into open boxes where I had entered a prompt.

This can be reproduced by clicking into the first one at the very top, but in some cases also by clicking into existing ones after scrolling upward.

Steps to Reproduce

see desc

Operating System

Windows 10/11

Version Information

Version: 2.6.19
VSCode Version: 1.105.1
Commit: 224838f96445be37e3db643a163a817c15b36060
Date: 2026-03-12T04:07:27.435Z
Build Type: Stable
Release Track: Early Access
Electron: 39.4.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Linux x64 6.8.0-90-generic

Does this stop you from using Cursor

No - Cursor works, but with this issue

[deanrie]

Hey, thanks for the report. This is a known bug with scroll behavior in long chat conversations. When you click into a previous prompt box, the chat incorrectly jumps back to the bottom.

The team is aware of this issue. No ETA on a fix yet, but your report helps us prioritize it.

As a workaround for now, you can try:

• Using Ctrl + Up Arrow to move to previous prompts instead of scrolling and clicking
• Starting new chat sessions instead of working in very long conversations

Also, a quick note: your bug report says Windows 10/11, but the version info shows Linux x64. Are you running Cursor through WSL or over a remote connection?

Let me know if you have any questions.

[Benutzer4 (Info)]

Thank you very much for the quick response. I understand now. I use both, but I can only remember that I definitely had the issue on Linux.