My cursor w as working perfectly up until ~7 hours ago.
Cursor version v 0.46.8 on windows
-
Today, when i first started using it using Claude 3.7 i noticed it was taking an insane amount of time to apply a change (same for other models).
-
I opened up a new conversation to see if starting afresh would help, and found i was getting the same issue
-
After logging out/ in and restarting PC several times found no changes
-
Reached out to hi@cursor i was advised to check / try several things including:
- Not using VPN or Proxy: no issues
- Checked cursor is latest v 0.46.8
- checked background processes for efficiency: no issues
- disabled extensions: no issues / nothing active
- cleared cache %APPDATA%\Code\User\workspaceStorage\
- checked Toggle Developer Tools: …found several ‘’[‘composer] Failed to get complete AI response’'… ‘‘Error in AI response: ConnectError: [resource_exhausted]’’ in the logs
… Didnt manage to get anywhere as the issue was too advanced and was put into queue for further investigation.
- I restarted my pc in a last ditch effort to see if that would help resolve any issues, and upon attempting to open cursor I was met with the ‘setup process’ (the initial steps where you have to ‘install cursor’ command and import extensions etc…) I thought it was a glitch and restarted my PC again … same thing! ended up having to go through the install process again and upon completion I found that ALL of my previous chats from ALL of my workspaces are completely gone – … just restarting my pc, no setting changes, no edits to my system or permissions changes, nothing?
I can see some people have posted similar-ish issues but i’m flagging this because literally all my chats are gone and i dont see that reported. A day of lost productivity i can get over… but lost context from several past convos is sending me fr
Also when I first started getting this error i was ~200 fast requests out of 500… I’m now at 277 from receiving consistent error messages with not a single piece of usable output!
Please if anyone from the team could advise:
A. Can old chats be recovered/restored?
B. Is there a time scale on resolving this bug? (I’ve seen posts from 9+ days ago mentioning similar issues)
C. Can we appeal the use of fast requests on system errors (the requests I’ve used today from the constant errors are ~50 and nothing to show for it)
Screenshots
Kind regards,
Trace