Chat view scroll position resets when switching between conversations

Hey, thanks for bumping the thread again. I want to be honest: the previous fixes in 1.4.5, 1.7, etc. didn’t cover all edge cases, and the bug keeps coming back in different scenarios like chat to chat, chat to terminal, refresh after a long chat, WSL, and so on. We’re tracking this internally as a known issue, but I can’t share an ETA. It’s deeper than just restoring scroll position and it ties into the chat rendering architecture.

While we don’t have a fix, you can try a workaround from @chadacaldwell in post #53: open chats as editors via the three dot menu at the top, then Open Chat as Editor. When switching between those tabs, the scroll position tends to stay more stable.

@Sadegh_Karimi @jonassteinberg1 I’ve noted your versions 3.3.30 on WSL and 2.6.22 on macOS. If we have updates on the fix, we’ll post them here.

This issue still persists in Cursor 3.4.20 on macOS.

@deanrie

I’m also having this issue on Windows:

Version: 3.6.31 (system setup)
VS Code Extension API: 1.105.1
Commit: 81fcf2931d7687b4ff3f3017858d0c6dee7e2a60
Date: 2026-05-31T17:46:29.630Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
xterm.js: 6.1.0-beta.220
OS: Windows_NT x64 10.0.26200

“Open Chat as Editor” was a valid workaround last year, but since Cursor version 3 was introduced, chats are opened as editor by default; there is no longer a separate chat pane.

The workaround that works for me is right-clicking the tab and selecting “Move into new Window.” Although I would prefer to keep everything in the same window and just go back and forth between tabs as needed.

Ideally, we still want tabs to remain at their current scroll position when switching between conversations, not being reset to the bottom of the conversion or to the top of the conversation.

Hey, thanks for the update and for calling out the working workaround. It’s helpful for other users in the thread.

Confirmed: you’re right, Open Chat as Editor isn’t applicable in Cursor v3 anymore, since chats open as an editor by default and there’s no separate chat pane. Right now, Move into new Window right-click on the tab is the most stable workaround.

On the bug itself, the status is unchanged like I said earlier in the thread. It’s a known issue tracked internally, but I can’t share an exact ETA. The problem is deeper than just restoring scroll position and is tied to the chat rendering architecture, so fixes sometimes cover some cases but not all edge cases at once.

The expected behavior keeping the tab scroll position when switching, instead of jumping to the top or bottom is noted. I’ll post here when there are updates on a fix.

The issue is still present in the most recent update:

Version: 3.7.21 (system setup)
VS Code Extension API: 1.105.1
Commit: 517f696d8ab6c53eb04fbfdaae705cd146bf3460
Date: 2026-06-07T21:46:09.237Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
xterm.js: 6.1.0-beta.256
OS: Windows_NT x64 10.0.26200

The issue is still present in the most recent update:

Version: 3.7.36 (system setup)
VS Code Extension API: 1.105.1
Commit: 776d1f9d76df50a4e0aeca61819a88e7c1b861e0
Date: 2026-06-13T00:31:56.287Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
xterm.js: 6.1.0-beta.256
OS: Windows_NT x64 10.0.26200

On switching agent tabs in editor window. Often the view goes to the switched agent history top, not last viewed position. I have to scroll long down to restore previous view.

The issue is still present in the most recent update:

Version: 3.10.17 (system setup)
VS Code Extension API: 1.125.0
Commit: c89f45b831621cdc5e951694db44fecd8fab1150
Date: 2026-07-05T06:39:45.228Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256
OS: Windows_NT x64 10.0.26200

Confirming still present in the latest update…

Version: 3.12.17 (user setup)
VS Code Extension API: 1.128.0
Commit: 0fb762053c34788bb7760d5673f8a6d4c8589d50
Date: 2026-07-17T02:53:53.006Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256
OS: Windows_NT x64 10.0.26200

Wild that this has been open and unsolved for almost a year now.

Too busy pushing agent view to fix massive usability issues in the ide lol

Still present in the latest update! It’s honestly really annoying when switching between multiple chats. Can we please fix this, Cursor Team? Or does anyone know any temporary workarounds? Thanks for your help!