Cursor stop working when chat

[Moment]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

when I use chat model and let it check my code function. the ide will stuck and stop working. it cant do anything and i must kill the ide by windows task.

Steps to Reproduce

just select any func and chat to check the func problem,it will stuck.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.46 (user setup)
VSCode Version: 1.105.1
Commit: ab326d0767c02fb9847b342c43ea58275c4b1680
Date: 2025-12-02T03:59:29.283Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26100

For AI issues: which model did you use?

any model will stuck

Does this stop you from using Cursor

Yes - Cursor is unusable

[deanrie]

Hey, thanks for the report. The IDE freezes when sending code to chat - this is a serious issue.

Could you please share:

• Try launching with extensions disabled: cursor --disable-extensions from the Windows command line - does the freeze still happen?
• Open Help > Toggle Developer Tools > Console before the freeze and share a screenshot of errors (if it loads in time)
• How many tabs are open in the editor when it freezes? Try closing all tabs and reproduce on a single file
• Size of the function/file you’re sending to chat (lines of code)?
• Request ID: try with Privacy Mode off in chat and copy the Request ID (chat menu > Copy Request ID) before the freeze, if it sends

Similar issue (closing tabs helped): Cursor app becomes unresponsive and crashes after opening a project

Share the info, and if needed, I’ll pass it to the team.

[Moment]

i close all i need not extensions. but i stuck again.here its errors.

and i just open 3 tabs in the editor. i have to kill it again.

[deanrie]

Thanks for the screenshots! In the console, I see repeating:

• OTLPExporterError 400: “Trace spans collection is disabled for NO_STORAGE privacy mode” - you have Privacy Mode enabled (this prevents getting the Request ID, but shouldn’t freeze the window itself).

Let’s check this step by step and get the info back:

1. Full extension disable: launch from Windows terminal
   cursor --disable-extensions
   and confirm if the freeze persists.
2. Settings → Network → Run Diagnostics - send the result.
3. CTRL+Shift+P → Developer: Open Process Explorer - screenshot of processes with high CPU/RAM during the freeze.
4. Help → Toggle Developer Tools → Console - copy the error text (not screenshot) for a couple seconds before the freeze and right after.
5. In chat, temporarily disable Privacy Mode → chat menu → Copy Request ID and send the ID.
6. How many lines in the function/file being checked? Try reproducing in a new empty window on a small file (1 tab).

Send this data - if the freeze happens even with extensions/HTTP2 disabled, I’ll pass it to the team.

[Moment]

i disable extensions and the freeze again.

2.the result is like that

and sorry its all frozen,and i cant copy the error text,it cant select. and my file is golang file line count is 80.

[deanrie]

Thanks for the screenshots. From the diagnostics, I see: Chat/Agent “SSE responses are being buffered by a proxy” and TLS disconnects in the console - this looks a lot like a corporate proxy/VPN that’s buffering streaming and hanging the window.

What we’ll try:

• It’s good that HTTP Compatibility = HTTP/1.1. Additionally:

1. Disable VPN/corp proxy (Zscaler etc.) and check on another network/mobile hotspot - does the freeze reproduce?
2. Settings > Application (search “proxy”): Proxy Support = Off; clear http.proxy, restart Cursor.
3. Help > Toggle Developer Tools > Console - if possible, send the text of the latest errors again.
4. Settings > Network > Run Diagnostics > Show Logs - send the log text (not screenshot).
5. In chat, temporarily disable Privacy Mode and send Request ID (chat menu > Copy Request ID).

If it’s fine without proxy/on another network - that confirms the cause is SSE buffering.

[alphax (alpha)]

I have a similar issue when, but in WSL
2025-12-04 17:31:12.628 [error] Failed to patch code.sh launcher: Error: ENOENT: no such file or directory, open ‘c:\Users\alphja\AppData\Local\Programs\cursor\resources\app\bin\code’

2025-12-04 17:31:12.628 [info] Resolving wsl remote authority ‘wsl+ubuntu-24.04’ (attempt #1)

2025-12-04 17:31:12.628 [info] Installing cursor-server with options: {“id”:“a227bb470acb6f1c1af9eef3”,“commit”:“2d3ce3499c15efd55b6b8538ea255eb7ba4266b0”,“line”:“production”,“realCommit”:“2d3ce3499c15efd55b6b8538ea255eb7ba4266b2”,“extensionIds”:,“serverApplicationName”:“cursor-server”,“serverDataFolderName”:“.cursor-server”,“forceReinstall”:false,“killRunningServers”:false}

2025-12-04 17:31:12.910 [info] [wsl exec: installServerScript][stderr]: your 131072x1 screen size is bogus. expect trouble

2025-12-04 17:31:13.065 [info] Successfully connected to Cursor server at http://127.0.0.1:43983/version from Windows

2025-12-04 17:31:13.065 [info] Returning resolved authority for Cursor server at http://127.0.0.1:43983/version from Windows. Returning token: fed7cd6e-28da-4ace-9f6d-86c4edee3788

2025-12-04 17:31:56.452 [info] Resolving wsl remote authority ‘wsl+ubuntu-24.04’ (attempt #2)

2025-12-04 17:31:56.466 [warning] Failed to reuse existing connection, attempt 1 of 2 fetch failed

2025-12-04 17:31:56.574 [warning] Failed to reuse existing connection, attempt 2 of 2 fetch failed

2025-12-04 17:31:56.971 [info] Installing cursor-server with options: {“id”:“17a8c2deb4b9552366bd0e8b”,“commit”:“2d3ce3499c15efd55b6b8538ea255eb7ba4266b0”,“line”:“production”,“realCommit”:“2d3ce3499c15efd55b6b8538ea255eb7ba4266b2”,“extensionIds”:,“serverApplicationName”:“cursor-server”,“serverDataFolderName”:“.cursor-server”,“forceReinstall”:false,“killRunningServers”:false}

2025-12-04 17:31:57.249 [error] Error installing Cursor server [wsl exec: installServerScript] Command failed with exit code 4294967295: stdout: Catastrophic failure

Error code: Wsl/Service/E_UNEXPECTED

[Jannie_Gill]

I hit the same issue recently — for me it happened because an extension was clashing with Cursor when the chat panel opened. Disabling a couple of them and restarting Cursor fixed it right away. You could also try clearing the workspace cache. Usually one of those gets it working again.

[Moment]

I try to disable some python extension and clear the workspace cache. now the chat works ok and not frozen again. But i dont know which used.

[Moment]

sorry for that,it frozen again! and this time i clean the workspace cache but useless.it almost stuck everytime now,I cant work with it at all.please tell me how to solve this problem.

extension now I just have go,gitlens and rainbow csv

and I just for solve the problem update. now my version is

Version: 2.1.50 (system setup)
VSCode Version: 1.105.1
Commit: 56f0a83df8e9eb48585fcc4858a9440db4cc7770
Date: 2025-12-06T23:39:52.834Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200

[Moment]

Hello,have any new function can solve my problem

[deanrie]

Hey, thanks for coming back. I see the issue reproduces almost every time, even after clearing cache and updating to 2.1.50.

From the thread history (listener leak 175+ in console, SSE buffering in diagnostics), it’s a combo of network issues and resource buildup.

Try without deleting data:

1. Settings > Network > make sure “Disable HTTP/2” is on, restart Cursor
2. Settings > Application > search “proxy” > Proxy Support = Off, clear http.proxy field, restart
3. Disable VPN/corp proxy (if any) and test on mobile hotspot
4. Open new empty window with one small file - does hanging reproduce?

Can you please share:

• Confirmation if it reproduces on another network (no VPN)?
• Settings > Network > Run Diagnostics > Show Logs - log text (not screenshot)
• Request ID with Privacy Mode off (chat menu > Copy Request ID) - if you catch it before hanging
• Ctrl+Shift+P > Developer: Open Process Explorer - screenshot of high CPU/RAM processes during hanging

Let me know the results.

[Leo_Caesar]

Just want to piggyback on this. It actually happened to both VSCode and Cursor. Similar to your incident.