[2.6.11] Clicking On Chat in Chat History Not Working

Describe the Bug

Clicking on chat from chat history does not go to that chat.

Steps to Reproduce

Have several chats in chat history and click one.

Expected Behavior

Closes chat history and makes the clicked chat active.

Operating System

Windows 10/11

Version Information

Version: 2.6.11 (user setup)
VSCode Version: 1.105.1
Commit: 8c95649f251a168cc4bb34c89531fae7db4bd990
Date: 2026-03-03T18:57:48.001Z
Build Type: Stable
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: Windows_NT x64 10.0.19045

Does this stop you from using Cursor

No - Cursor works, but with this issue

4 Likes

This seem to be resolved when I clicked the double arrow icon at the top right, this then changed my layout/view and made the chat panel look a bit different. Then the chat history worked.

3 Likes

Thank you so much! Had the same issue and that worked for me as well

If you do Ctrl + E (windows) or Cmd + E (mac) until the double arrows is seen, the issue returns.

image

This appears to be the shortcut for “Swap Agent Sidebar Location”

And this layout state is preferable because it allows for the undo/keep to appear as an overlay instead of in breadcrumbs.

image

Hey, thanks for the report and for finding a workaround, and especially for the detail about Ctrl+E. This is a known bug in 2.6.11, there’s another thread with the same issue here: Chat sessions history

The team is aware. The info that the issue is tied to a specific layout state (Swap Agent Sidebar Location) is really helpful, I’ll pass it along to the team.

Let me know if anything else comes up.

1 Like

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Whenever I am trying to switch chats via Show chat history icon on the top right, it shows all the previous chats in the usual dropdown but when I click, nothing happens. I can only create new chats but the old ones aren’t opening. No updates are pending for the IDE, any help please?

Steps to Reproduce

  1. Open Cursoer
  2. Click on the clock icon on top right
  3. Either no dropdown shows up or if it shows previous chats then clicking on those chats does not do anything

Operating System

MacOS

Version Information

Version: 2.6.12
VSCode Version: 1.105.1
Commit: 1917e900a0c4b0111dc7975777cfff60853059d0
Date: 2026-03-04T21:41:18.914Z
Build Type: Stable
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

This appears solved in 2.6.13

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

I just updated to the newest version of cursor and ran into an issue where when I press the clock icon, select a previous chat, then nothing happens. I’m not taken to the other chat and instead am stuck with the one I was already on. However, selecting a different chat on the bar above the chat still works. I asked my team and it sounds like it’s not just me, my coworker has a Windows machine that also is having the same issue. I have a Mac.

Version: 2.6.12
VSCode Version: 1.105.1
Commit: 1917e900a0c4b0111dc7975777cfff60853059d0
Date: 2026-03-04T21:41:18.914Z
Build Type: Stable
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

Steps to Reproduce

To reproduce is pretty easy, just open up cursor, press the clock icon, and try selecting a different chat then the one you’re on.

Expected Behavior

I’m expecting to be taken to the chat I selected, but instead nothing happens. And sometimes the clock icon becomes unresponsive as a whole until I select a chat via the slide bar above the chat. then I can press the clock icon again.

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Version: 2.6.12
VSCode Version: 1.105.1
Commit: 1917e900a0c4b0111dc7975777cfff60853059d0
Date: 2026-03-04T21:41:18.914Z
Build Type: Stable
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

No - Cursor works, but with this issue