Hey, this is a known issue. The backend is processing your requests successfully, but the responses aren’t showing up in the chat UI. Since you haven’t used Cursor in a while, your project index is probably out of date.
Try this first. It’s been the most effective fix:
Reindex the project database: Cmd + Shift + J > Indexing & Docs > Reindex. Wait for it to finish, then start a new chat.
If that doesn’t help:
Test in an empty folder: File > Open Folder > pick an empty directory, open a new chat, type “hello”. Does it respond?
Disable HTTP/2: Add this to your settings.json (Cmd + Shift + P > Preferences: Open User Settings (JSON)):
"cursor.general.disableHttp2": true
Restart Cursor after.
Run network diagnostics: Cursor Settings > Network > Run Diagnostics. Share a screenshot if anything looks off.
Hi, reindexing didn’t appear to do much in this case but disabling http2 and restarting seems to have freed it up. The diagnostics seem to all run well. Will report back if i have more issues
EDIT: Actually, I was wrong. It still just sits there and does nothing.
When you say ‘reindex’ … do you mean ‘Delete Index’ and then ‘Compute Index’ … or do you mean ‘sync’ ?? There is no ‘reindex’ button in my settings > Indexing & Docs >
OK. I have moved onto getting nightly versions to see if I can actually get cursor to work. I have disabled http2 and started a fresh project. In the new project it actually briefly responded to something, started to write some very basic html and then just hung again
I see the issue still isn’t gone. I’ll reply step by step.
About reindex, yes, you need to click Delete Index, then Compute Index. This will rebuild the index from scratch. Wait until it fully finishes, then open a new chat.
The fact that it worked for a short time in an empty project on nightly, then froze again, is an important detail. Can you also try this:
When the chat freezes, copy the Request ID: open the chat context menu icon in the top right, then select Copy Request ID. Send it here. This will help us narrow down what’s happening on the client side.
Check network diagnostics: Cursor Settings > Network > Run Diagnostics.
If you’re using a VPN or proxy, try without it.
This is a known issue and the team is aware. But we really need the Request ID for further debugging.
