Agent/Chat panel scroll jumps to the top of the thread in long conversations (3.17.19, Windows 11)

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Scrolling an Agent/Chat conversation in the editor panel frequently jumps the viewport all the way back to the top of the thread instead of scrolling by a normal increment. It happens both with the mouse wheel and when dragging the scrollbar, and it is worst in long conversations that contain many tool results and large code blocks (C#, TypeScript, HTML).

Once it snaps to the top, I lose my reading position and have to scroll or search my way back down.

This looks related to the known “scroll reset” cluster that staff have acknowledged (chat remounting, e.g. toggling the Agents panel), but in my case it also happens during plain scrolling of an in-progress conversation, without switching tabs, switching conversations, or toggling any panel.

Steps to Reproduce

  1. Open Cursor 3.17.19 on Windows 11.
  2. Start an Agent conversation in the editor chat panel and let it run long enough to contain many tool calls/results and several large code blocks (C#, TypeScript, HTML).
  3. While the agent is still working, scroll up into the middle of the thread to read earlier output.
  4. Keep scrolling with the mouse wheel, or drag the scrollbar a small amount.

Actual result: the panel frequently snaps to the very top of the conversation instead of moving incrementally. It repeats often within the same conversation and gets more frequent the longer the thread grows.

I can capture a screen recording of the jump if that would help reproduce it - happy to attach one.

Expected Behavior

The scroll position should stay where I put it. Mouse wheel and scrollbar input should move the view by the corresponding increment, and new streaming content further down the thread should never yank the viewport back to the top of the conversation.

Operating System

Windows 10/11

Version Information

Cursor IDE 3.17.19 (user setup), installed 2026-08-24
OS: Windows 11 (win32 10.0.26200)
Install path: C:\Users\scarlisle\AppData\Local\Programs\cursor

(Full About Cursor copy string not captured at time of filing - can add commit/build hashes on request.)

Additional Information

What I already checked before filing:

  • The docs don’t describe auto-scroll / jump-to-top behavior, and there’s no setting I can find to preserve scroll position.
  • Changelog 3.0 added a “scroll to bottom” button when content overflows.
  • Changelog 3.1 mentions smoother long-conversation scrolling / less stutter, and 3.4 mentions improved long-chat scrolling while streaming. Both are smoothness improvements, not preserving a mid-thread position.
  • I upgraded to 3.17.19 specifically hoping this was fixed. The 3.17 changelog doesn’t mention a jump-to-top fix, and the behavior is still present.
  • Staff have previously described jump-to-top as a known scroll-reset cluster tied to chat remounts (for example toggling the Agents panel), with no ETA as of June 2026.

Possibly related existing topics (link limit for new accounts, so listing by topic ID):

  • 127336 - “Chat view scroll position resets when switching between conversations”
  • 164029 - “Toggle agents with ctrl+alt+j goes top”
  • 160981 - “Agent tab switch goes top”

Difference from those: mine also reproduces during ordinary wheel/scrollbar scrolling inside a single in-progress conversation, with no tab switch, conversation switch, or panel toggle involved.

Workarounds I’m using (none are fixes): keeping the Agents panel open, setting tool call density to Compact, using the scroll-to-bottom button, and Ctrl+F inside the conversation to get back to where I was reading.

Happy to provide a screen recording if that helps pin down the trigger.

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey @Steve_Carlisle
What you’re seeing isn’t intended behavior and isn’t anything on your end. It’s an issue we’re tracking.

Could you attach the screen recording you offered (with the scrollbar visible during the jump) and paste the full version string from Help → About? That’s exactly what we need to dig in. Compact tool-call density and starting a fresh chat once threads get long will reduce how often it fires in the meantime.

Thanks Mohit,

It is, of course, not doing it now. I think the conversation got too large and it summarized it and the problem went away. Basically I was using the wheel to scroll up (to find the top of the last answer) and after several (3-7) scrolls it would just jump to the top of the whole conversation. I don’t have a visible scrollbar which would be a helpful thing to have. Here’s the relevant portion of the application.