Agent "Changes" list sometimes missing; blocks not clickable after restart (Windows, 3.10.17)

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

After updating to Cursor 3.10.17, the Agent “Changes” section in chat behaves inconsistently in ways that appear separate from the known “unresponsive click” issue.

I see two related symptoms:

Changes list sometimes does not appear at all
After the Agent completes file edits, no “Changes” / diff block is shown in chat. The edits are applied to files, but there is no clickable summary in the conversation.

Clickable blocks disappear after fully closing and reopening Cursor
If a “Changes” block was clickable in a session, after I fully quit Cursor and reopen it, those blocks in chat history are no longer clickable (or the interactive Changes UI is gone). This makes it harder to navigate back to edited files from previous sessions.

This is intermittent: in some sessions the Changes list appears and works; in others it is missing or becomes non-interactive after restart.

Steps to Reproduce

Open a project in Cursor and start a chat with the Agent.
Ask the Agent to modify one or more files.
Wait for edits to complete.
Observe whether a “Changes” block appears in chat.
If it appears and is clickable, fully quit Cursor (not just Reload Window), reopen the same project/chat, and try clicking the same Changes block again.

Expected Behavior

After every Agent edit, a “Changes” / diff summary should appear in chat.
Changes blocks in chat history should remain clickable after restarting Cursor, opening the affected file at the changed lines.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 3.10.17 (user 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

For AI issues: which model did you use?

Auto

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

5

After fully closing and reopening Cursor, clickability is lost mostly for newer Changes/diff blocks. In some older chat sessions, clickability can also disappear.

6

I think the current bug is related to this issue:
https://forum.cursor.com/t/agent-changes-list-sometimes-missing-blocks-not-clickable-after-restart-windows-3-10-17/165004

8

Thanks for the detailed report and for moving it into a separate thread.

We know both symptoms, and both are client-side renderer issues. We don’t see any related errors reaching the backend in logs. Important note: your edits are always written to disk no matter whether the Changes block shows up in chat. Nothing is lost.

About the symptoms:

  1. The Changes block sometimes doesn’t show up at all after the agent edits. This is a known bug related to the end-of-turn summary disappearing. A fix is on the way and it should be addressed in one of the next updates.

  2. Blocks stop being clickable after fully closing and reopening Cursor. This is in the same cluster as this thread: Cursor Agent Diff/Change Links Unresponsive. By design, pending review should survive a restart. If it disappears, or clicking an old block silently does nothing (for example the file was renamed or moved, or the workspace context hasn’t finished loading after a cold start), that’s a bug, not auto-accept. No ETA yet.

Workaround:

  • Before you fully quit, hit Keep or Undo for files in the Review panel, or commit your work.
  • If an old Changes block won’t open a file, open it manually or via the diff or Review tab.

If symptom 1 still happens after the next updates, let us know and we’ll take another look.

9

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

the animations seem to have been updated with the chat window in the ide and there are two bugs that ive found.

  1. Code change blocks get removed or hidden from the chat if you change chats and back
  2. you can no loonger click on the title of the code block to open the file

Steps to Reproduce

  1. get ai to make a change, switch to different chat, switch back to original chat
  2. get ai to make a change, try and click on the top of the code block (where it says the file name - highlighted in pink dotted area in the second screenshot)

Expected Behavior

  1. the code blocks should stay there
  2. should open the file when clicking on the top bar (has done since ive been using cursor)

Screenshots / Screen Recordings

1. showing missing code blocks (pink boxes)
1. showing missing code blocks (pink boxes)500×768 30.6 KB
2. the area which upon clicking should open the file
2. the area which upon clicking should open the file484×141 12 KB

Operating System

Windows 10/11

Version Information

Version: 3.10.17 (user 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.19045

Does this stop you from using Cursor

No - Cursor works, but with this issue

10

I’ve observed both of these behaviors in MacOS as well.

11

I have the same problem, and I hope it gets fixed soon. When will the update be released?

12

I installed an update. I restarted the cursor. The problem still persists.

When I restart CURSOR, all the boxes disappear.

Version: 3.10.20 (user setup)
VS Code Extension API: 1.125.0
Commit: 23b9fb205fe595ea2be29da7214e19762d037fc0
Date: 2026-07-07T07:03:33.071Z
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

13

Thanks everyone for the updates, and for confirming that yes, this behavior isn’t Windows-specific. It reproduces on macOS too.

It’s important to separate two symptoms, since we’re tracking them separately:

  1. The Changes block sometimes doesn’t show up after the agent makes edits. This is the issue the recent updates were targeting.

  2. Blocks disappear or become unclickable after a full restart of Cursor. This is a separate client-side issue, and it’s not fixed yet. I don’t have an ETA for it. @GuzillaHL, that’s why you still see it on 3.10.20. The update was about item 1, but you’re hitting item 2.

For both symptoms, the edits are always saved to disk no matter whether the block shows up in chat or not. Nothing is lost, it’s purely a UI display and interaction issue.

Workaround until a fix lands:

  • Before fully closing Cursor, click Keep or Undo for the files in the Review panel, or commit your work.
  • If an old Changes block won’t open a file, open the file manually or via the diff or Review tab.

If item 1 comes back after the next updates, post here and we’ll take another look.

14

YEAH. It’s working again :partying_face:

Version: 3.11.13 (user setup)
VS Code Extension API: 1.125.0
Commit: 3f21b08f0b436a07be29fbfe00b304fa15553350
Date: 2026-07-10T01:45:28.254Z
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