Background:
I initially had automatic apply disabled. That option has since disappeared, and I believe my current issues are related to that functionality.
Issue:
When I use composer for more than a couple turns, the ability to apply diffs goes away. It will always say ‘reapply’, but if i select reapply, it will just regenerate the response, not apply the changes initially proposed.
For now I’m having to just copy paste things over which is tedious.
Anyone else having this issue?
Thanks!
Same issue here. I reported this yesterday. Welcome aboard the credit wasting train! 
Hi @preston ,
I also experienced this yesterday on Windows at Cursor 0.40.3.
Thanks for reporting it and explaining it so clearly.
Having clear steps to reproduce, and related screenshots and system info really helps the devs fix things.
I didn’t have time to look through all the logs when it happened to me, but I plan to do that when I am back at the computer.
I will be looking in all the usual places, ie:
01) Developer tools console errors
Open developer tools via:
Cursor > Help > Toggle Developer Tools
and then click Console and see if there are any related errors.
02) Logs
On Windows, you can find logs here:
C:\Users\<your-user-name>\AppData\Roaming\Cursor\logs
This is the parent folder of the folder that is opened when doing:
Ctrl + Shift + P (to open command palette in Cursor)
Typing and selecting Developer: Open Logs Folder
You can also view logs in Cursor > Terminal > Output and then click on the dropdown and select Window or one of the other Cursor specific options, such as Cursor Tab or Cursor Indexing & Retrieval.
That’s helpful, I didn’t realize cursor had that kind of debugging functionality out of the box so I’ll see what I can find and then report back if I find anything useful.
Preston
Same here with regular chat. Apply stopped applying randomly, nothing is happening.
Edit: now seems to be working again.
@fun_strange did you do anything at all? or did it start by itself?
Perhaps your logs might give some clues if you can see any changes between the time it stopped working and when it restarted?
Happy for you though mate
It stopped applying for a single chat, and then I started a new chat and it started working again. During that non-working session I had to manually copy the code into the editor. Unfortunately I wouldn’t be able to find the logs anymore
I’m almost afraid to say that it also seems to be working for me now. Haven’t updated though, i was on 40.3 already so not sure. Will post back if I have the issue again.
Thanks both.
Lets hope I get some of the fairy dust sprinkled over my Cursor today.
So the issue definitely has not resolved itself.
I have been watching the logs, and there are plenty of errors that pop up when a file has been moved and cursor does not realize it, or errors like this:
workbench.desktop.main.js:21968 ERROR WHEN RENDERING SOLID COMPONENT TypeError: Cannot read properties of undefined (reading 'tabId')
at workbench.desktop.main.js:23011:16541
at Object.fn (workbench.desktop.main.js:1452:58041)
at Je (workbench.desktop.main.js:280:45634)
at Ue (workbench.desktop.main.js:280:45401)
at We (workbench.desktop.main.js:280:47023)
at Ae (workbench.desktop.main.js:280:48274)
at workbench.desktop.main.js:280:47888
at Ce (workbench.desktop.main.js:280:47203)
at De (workbench.desktop.main.js:280:47881)
at Ce (workbench.desktop.main.js:280:47215)
at oe (workbench.desktop.main.js:280:42413)
at A.x [as setChatData] (workbench.desktop.main.js:280:76816)
at m.value (workbench.desktop.main.js:23360:1284)
at T.B (workbench.desktop.main.js:445:732)
at T.C (workbench.desktop.main.js:445:802)
at T.fire (workbench.desktop.main.js:445:1018)
at T.fire (workbench.desktop.main.js:445:2147)
at u.setContext (workbench.desktop.main.js:1100:208206)
at r.set (workbench.desktop.main.js:1100:206536)
at Ve.showChatHistory (workbench.desktop.main.js:23390:17166)
at Je.showChatHistory (workbench.desktop.main.js:23390:5113)
at H.run (workbench.desktop.main.js:23390:18900)
at handler (workbench.desktop.main.js:1174:21540)
at p.invokeFunction (workbench.desktop.main.js:1103:685)
at d.n (workbench.desktop.main.js:21391:32694)
at d.executeCommand (workbench.desktop.main.js:21391:32282)
at l.run (workbench.desktop.main.js:1174:21184)
at v.q (workbench.desktop.main.js:486:20798)
at v.run (workbench.desktop.main.js:486:20725)
at D.onClick (workbench.desktop.main.js:1247:117809)
at HTMLLIElement.<anonymous> (workbench.desktop.main.js:724:10912)
console.error @ workbench.desktop.main.js:21968
Not sure they are related though.
Here is what seems to cause the issue:
Selecting ‘reapply’ will generate a new response, but you will end up with the same result. You cannot apply. Clicking save, apply or reject do nothing.
Screenshot:
