Cursor times out like 60s up to 10 min everytime it does a file edit
See this Loom: https://www.loom.com/share/f92adb01f9c145fa85451a38917d77cb
Bug introduced in recent v2 updates. Same computer, same RAM, no issues before the v2 upgrade
Steps to Reproduce
Just ask Cursor to edit a file.
Expected Behavior
Should be fast as before
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Hey, thanks for the report. I know this is frustrating, especially since everything was working fine before v2.
To help debug these timeouts, could you please share:
Request ID: after a slow file edit, click the chat menu (top right of the chat panel) → “Copy Request ID”
Extensions check: CMD+Shift+P → “Developer: Open Extension Monitor” → check if any extensions show high CPU usage or long activation time during the hang
Process info: during a timeout, run CMD+Shift+P → “Developer: Open Process Explorer” → take a screenshot of what’s using resources
Thanks for the network diagnostics! They show two issues that are causing your timeouts:
Primary issue - network proxy blocking Agent: the diagnostics show that Agent streaming is being blocked by an HTTP/2 proxy. Please try disabling HTTP/2:
Open Cursor Settings (CMD+,) → search for “HTTP/2” → enable “Disable HTTP/2”
Restart Cursor
Test a file edit
Secondary issue - memory bloat: your sharedProcess is at 4.61 GB, which is abnormally high (it should be under 100 MB). This is a known v2.0 globalStorage bloat:
Close Cursor
Go to: ~/Library/Application Support/Cursor/User/globalStorage/
Rename or backup the files state.vscdb and state.vscdb.backup
Restart Cursor
Disabling HTTP/2 should fix the Agent timeouts. Cleaning up the storage will improve overall performance. Try the HTTP/2 fix first and let me know if file edits work after that.