Have been using Cursor for more than a month now, suddendly it got extremely slow, practically unusable. Restarted Cursor, PC, checked connection ect, to no avail. Is it having issues on your side?
I too am having issues, not that it’s running slow, but it’s lying/hallucinating a crazy amount!! I had to shut it down and use a different LLM to work with.
Hey, I need a bit more detail so we can figure this out:
- What exactly is slow, the editor itself UI is laggy, typing is slow, or the AI requests chat or agent take a long time to respond or hang?
- Cursor version: Help > About Cursor > Copy
- What OS are you using?
Also try this:
- Network diagnostics: Cursor Settings > Network > Run Diagnostics, then paste the result here
- Disable HTTP/2: App Settings
Cmd+,orCtrl+,> search for HTTP/2 > turn on Disable HTTP/2 - Make sure you’re on the latest version: Help > Check for Updates
There are similar reports from other users in the last few days: Requests Extremely Slow & Stuck, Mass Wasted Calls and the team is aware. If it’s AI requests, please share a couple Request IDs right corner menu in chat > Copy Request ID, it’ll help us track what’s happening on the backend.
Hey @deanrie, I’ve seen the same since a few builds. Like, I literally can’t use the IDE for some time. When I try force quitting, I see it takes 30 GB. The rest of the application spikes to 5-7GB at max. And with the latest 3.0, if I open the agent window, within 5 mins, the whole system stops responding.
Hey, Same issue for me continuing today Apr 8th. I’m on Mac using Cursor Version: 3.0.13 (Universal), no updates available. Http compatibility mode set to http/1.1
Network diagnostics results:
Cursor Network Diagnostic Results
DNS: Success
Logs :
[2026-04-08T17:57:09.487Z] Host: api2.cursor. sh
[2026-04-08T17:57:09.488Z] Servers: [REDACTED IPV6], [REDACTED LOCAL IP]
[2026-04-08T17:57:09.488Z] Resolved to 3.216.212.206 in 3ms
[2026-04-08T17:57:10.162Z] Resolved to 3.90.75.202 in 663ms
[2026-04-08T17:57:10.165Z] Resolved to 3.90.75.202 in 2ms
[2026-04-08T17:57:10.167Z] Resolved to 3.90.75.202 in 2ms
[2026-04-08T17:57:10.172Z] Host: api2.c ursor.sh
[2026-04-08T17:57:10.172Z] Server s: system
[2026-04-08T17:57:10.172Z] Resolved to 3.90.75.202, 3.222.14.252, 3.228.121.15, 52.3.138.207, 100.50.91.228, 3.217.129.79, 34.236.188.122, 52.21.191. 134 in 1ms
[2026-04-08T17:57:10.173Z] Resolved to 3.90.75.202, 3.222.14.252, 3.228.121.15, 52.3.138.207, 100.50.91.228, 3.217.129.79, 34.236.188.122, 52.21.191 .134 in 0ms
[2026-04-08T17:57:10.173Z] Resolved to 3.90.75.202, 3.222.14.252, 3.228.121.15, 52.3.138.207, 100.50.91.228, 3.217.129.79, 34.236.188.122, 52.21.19 1.134 in 0ms
[2026-04-08T17:57:10.173Z] Resolved to 3.90.75.202, 3.222.14.252, 3.228.121.15, 52.3.138.207, 100.50.91.228, 3.217.129.79, 34.236.188.122, 52.21.1 91.134 in 0ms
[2026-04-08T17:57:10.173Z ] Result: true
SSL: Success
Logs:
[2026-04-08T17: 57:09.433Z] Start
[2026-04-08T17:57:09.758Z] URL: https ://api2.cursor.sh/
[2026-04-08T17:57:0 9.758Z] Status: 200
[2026-04-08T17:57:09.7 58Z] IP: 52.1.242.15
[2026-04-08T17:57:09.758Z] Issuer: C=US; O=Amazon; C N=Amazon RSA 2048 M01
[2026-04-08T17:57:09.758Z ] Name: api2.cursor.sh
[2026-04-08T17:57:09.758Z] AltName: DNS:api2.cursor.sh, DNS:prod.authentication.cursor.s h, DNS:*.api2.cursor.sh
[2026-04-08T17:5 7:09.758Z] DNS Time: 3ms
[2026-04-08T17:57:09. 758Z] Connect Time: 141ms
[2026-04-08T17: 57:09.758Z] TLS Time: 33ms
[2026-04-08T17:57:09. 758Z] Result: tru e in 325 ms
API: Success
Logs:
[2 026-04-08T17:57:09.444Z] Start
[2026-04 -08T17:57:10.424Z] Result: true
Ping: Success
Logs:
[2026-0 4-08T17:57:09.454Z] Sending ping 1
[2026-04-08T17:57: 10.601Z] Response: ‘ping’ in 1147ms
[2026 -04-08T17:57:10.601Z] Sending ping 2
[2026-04-08T17: 57:10.938Z] Response: ‘ping’ in 337ms
[20 26-04-08T17:57:10.938Z] Sending ping 3
[2026-04-08T1 7:57:11.271Z] Response: ‘ping’ in 333ms
[ 2026-04-08T17:57:11.272Z] Sending ping 4
[2026-04-08 T17:57:11.525Z] Response: ‘ping’ in 253ms
[2026-04-08T17:57:11.525Z] Sending ping 5
[2026-04- 08T17:57:11.774Z] Response: ‘ping’ in 249ms
[2026-04-08T1 7:57:11. 774Z] Result: true
Chat: Running
Logs:
[2026-04-08T17:57:09.465Z] Starting streamSSE
[20 26-04-08T17:57:10.465Z] Response: ‘foo’ in 989ms
[20 26-04-08T17:57:11.534Z] Response: ‘foo’ in 1069ms
[2 026-04-08T17:57:12.539Z] Response: ‘foo’ in 1005ms
[ 2026-04-08T17:57:13 .543Z] R esponse: ‘foo’ in 1004ms
Agent: Running
Logs:
[2026-04-08T17:57:09.475Z] Starting strea m
[2026-04-08T17:57:09.476Z] Pushing first message
[2026-04-08T17:57:10.601Z] Response: ‘foo’ in 1125ms
[2026-04-08T17:57:11.105Z] Pushing next mess age
[2026-04-08T17:57:11.410Z] Response: ‘foo’ in 809ms
[2026-04-08T17:57:11.910Z] Pushing next me ssage
[2026-04-08T17:57:12.285Z] Response: 'foo ’ in 875ms
[2026-04-08T17:57:12.788Z] Pushing next message
[2026-04-08T17:57:13.184Z] Response: ‘f oo’ in 899ms
[2026-0 4-08T17: 57:13.685Z] Pushing next message
Marketplace: Success
L ogs:
[2026-04-08T17:57:09.385Z] Host: market place.cursorapi.com
[2026-04-08T17:57:09 .772Z] Response in 387ms
[2026-04-08T17:57:09. 772Z] Response: 200
[2026-04-08T17:57:0 9.772Z] Response Type: cors
[2026-04-08T17:57: 09.772Z] Server: null
[ 2026-04- 08T17:57:09.772Z] Result: OK in 387ms
Authentication: Success
Logs:
[2026-04-08T17:57:09.398Z] Host: prod.aut hentication.cursor.sh
[202 6-04-08T 17:57:09.937Z] Response: 200 in 539ms
Authentication UI: Succ ess
Logs:
[2026-04-08T17:57:09.434Z] DNS lookup: authenticator.cursor.sh
[202 6-04-08T17:57:09.629Z] R esolved authenticator.cursor.sh to 172.64.152.23 in 192ms
Cur sor Tab: Success
Logs:
[2026-04-08T17:57:09.435Z] DNS lookup: api3.cursor. sh
[2026-04-08T17:57:10 .466Z] R esolved api3.cursor.sh to 104.18.18.125 in 1029ms
Agent End point: Success
Logs:
[2026-04-08T17:57:09.435Z] DNS lookup: agent.api5.cursor.sh
[2026-04-08T17:57:09.964Z ] Resolv ed agent.api5.cursor.sh to 100.30.166.181 in 522ms
Code base Indexing: Success
Logs:
[2026-04-08T17:57:09.436Z] DNS lookup: repo42.c ursor.sh
[2026-04- 08T17:57 :10.141Z] Resolved repo42.cursor.sh to 54.173.141.234 in 7 03ms
Downloads: Success
Logs:
[2026-04-08T 17:57:09.426Z] Ho st: down loads.cursor.com
[2026-04-08T17:57:10.126Z] Res ponse: 403 in 700ms
CDN: Success
Logs:
[2 026-04-08T17:57:09.433Z] Host: cursor-cdn.com
[2026-04-08T17:57:10.113Z] Response: 404 in 680ms
For me the UI is quite laggy, waiting on a response after clicking on something takes a while. For example opening the Git diff view for a changed file, even if the file is quite small and contains only few changes, takes a couple of seconds. I have noticed this issue only after upgrading the IDE to version 3.
I am using Cursor 3.0.13 on a Macbook M3 Pro running on macOS 26.3.1 (a).
Have been experiencing the same issue for last 5 days.
- Issue: Chat unusable, send message and thinks forever - completely stuck/stale
- Cursor:
Version: 3.0.12 (Universal)
VSCode Version: 1.105.1
Commit: a80ff7dfcaa45d7750f6e30be457261379c29b00
Date: 2026-04-04T00:13:18.452Z
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
OS: Darwin arm64 24.5.0
One more. Updated this morning, totally unusable, things that dont work:
Everything basically. Not even the file Search works
Mac M4, Cursor 3.0.13
I had to downgrade to CursorSetup-x64-2.6.22.exe in order to make it run faster.
3.x was way too slow!
yes,. cursor is slowly in my macbook pro M4, so this is a problem of softwara. we need fix b ecause in this moment cursor is unusable.
Its not letting me send more stuff as new to this chat. Is anyone looking into this?
Hey, looks like a few different issues got mixed together here. I’ll reply to each one.
@GB_e_Giada_Aicardi: Is the original issue still happening? The details in Post #4 will help a lot. Without them it’s hard to tell what’s causing it.
@Mr.Minnu: 30 GB memory use and freezing when opening the agent window on 3.0 is a known issue on macOS in 3.0.13. The team is aware. For now, please try:
- Close the agent window if you’re not using it
- Check your macOS version, which one exactly?
- If this is blocking you, you can roll back to 2.6.22 as a workaround
@Jerome_Gosset: The diagnostics look mostly fine, but ping latency is higher than normal, around 250 to 330 ms. What feels slow exactly, AI requests or the UI like switching tabs, opening files, git diff? If it’s AI, please share the Request ID: chat menu top right > Copy Request ID.
@Marjan_Extenteam: UI lag when opening git diff, and general lag after upgrading to 3.0, is also being tracked. Please try:
Cmd+Shift+P> Developer: Open Process Explorer and check which process is using resources- Run
cursor --disable-extensionsto rule out extensions
@marcmg: Chat freezes on 3.0.12. Please update to the latest version via Help > Check for Updates. Also share the Request ID from the stuck request so we can trace what’s happening on the backend.
@UnderTheMoonspell: Nothing works, even file search, on Mac M4 with 3.0.13. Please try:
- Run
cursor --disable-extensionsfrom Terminal - If that helps, it’s likely an extension issue. If it doesn’t, please share your macOS version and a screenshot of Process Explorer:
Cmd+Shift+P> Developer: Open Process Explorer
Performance issues on macOS in Cursor 3.0 are on the team’s radar. Your reports help us prioritize. Let me know what you find for each point above.
Check your macOS version, which one exactly?
Just FYI @deanrie
Hardware Overview:
Model Name: iMac
Model Identifier: Mac16,3
Model Number: MWV13HN/A
Chip: Apple M4
Total Number of Cores: 10 (4 Performance and 6 Efficiency)
Memory: 16 GB
System Firmware Version: 18000.120.27
OS Loader Version: 18000.120.27
Activation Lock Status: Enabled
System Software Overview:
System Version: macOS 26.5 (25F5042g)
Kernel Version: Darwin 25.5.0
Boot Volume: Macintosh HD
Boot Mode: Normal
Secure Virtual Memory: Enabled
System Integrity Protection: Enabled
I’m having more problems.
Code suggestions & AI chat are not working with no responses. Even TS warnings and type guard are not working. Literally nothing is working after Cursor update on Windows 10 while VSCode and Antigravity works fine.
What should I do? Pay more dollars??
Having issues with Cursor as well across multiple devices. When I restart my device and open Cursor, I am unable to open notebooks or load chats. The terminal also doesn’t work. The only solution i have found is clearing all app data or deleting the workspace. This seems to be related to a large chat history but i would argue my chat wasn’t even large. I recently bought the Pro plan to test cursor but due to the instability might have to go back to PyCharm. It’s not practical to constantly clear app data or delete the workspace due to a relatively small chat.
Same issue as described by @TokenMenance, which has been intermittent for the past week or two any time I reboot or close a window. Never encountered this problem on Windows or Mac OS before 3.x version, and it is enough of an impediment that it would make me cancel ProPlus subscription and switch to another offering.
The utility offered by Cursor over and above other offerings is the smooth and very user-friendly UI. Frankly, if Cursor’s UI doesn’t function smoothly, let alone being bricked entirely, then the fact that it is a glorified reskin and repackaging of offerings available elsewhere becomes much harder to ignore. Your differentiator was good UI and smooth UX, what in the world has happened in 3.x?
Unusable for me as well. I switched to Opus4.6 for some serious architectural planning: willing to bear the additional expense. But it is hanging up and getting lost. Is this because of the purported 4.7 migration? Back to Codex5.3, I guess.
Hey, a few updates on this thread:
@TokenMenance, @crich011: this sounds like a known issue. After a reboot, chats and notebooks don’t load, the terminal doesn’t work, and the only fix is clearing the workspace or app data. We’re tracking it, but to better match your setup, please share:
- Your exact Cursor version: Help > About Cursor > Copy
- OS: macOS or Windows, and the version
- Workspace: single folder or multi-root with multiple folders added
- A screenshot from when chats and notebooks won’t open, including whether you see Taking a little while… or any other indicator
If you’re on 3.0.13 or earlier, try updating first: Help > Check for Updates. We recently shipped a fix for freezes on macOS Tahoe and a general performance fix for long requests.
@Michael_Tolson: to debug the hanging on Opus 4.6, we need the Request IDs for a couple of stuck requests chat, top right menu > Copy Request ID plus your Cursor version. Model migrations shouldn’t break inference. With the IDs we can check what’s happening on the backend.
For everyone seeing performance issues in 3.0: if it’s still slow after updating to the latest version, run cursor --disable-extensions in Terminal, then open Cmd+Shift+P > Developer: Open Process Explorer and check which processes are using CPU and RAM. A screenshot of Process Explorer helps a lot.
As other’s have said for about a week now, agents have become unusable… Even simple prompts take near an hour. It’s crawling, painfully slow. 
same here I keep getting a code 5 and crashing. How do we rollback to a different version?