I see this, at every startup, in one project folder, and Cursor is unusable (instantly fails every chat message request telling me there’s a timeout, even though it was instant).
It looks like something in my project history/database is broken and crashing an internal cursor component.
I do NOT have ANY extensions of any kind loaded.
(“Bisect” disables 0, which is correct - I have are none)
Steps to Reproduce
Start cursor
Expected Behavior
Can chat
Screenshots / Screen Recordings
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
I notice there’s a difference between the commercial and the user version of cursor - the commercial one has a feature that lets them export their chats and/or move them to other machines - we need this in the user version of cursor as well - can you ask your team to enable this?
I need to be able to move my chats (aka “agents”) from this broken folder, to my other laptop where Cursor still works.
Hey, thanks for the report. This looks like a known issue with the extension host that the team is working on. But since it only happens in one specific project folder, it makes me think the workspace data might be corrupted.
Try this workaround:
Fully close Cursor
Find the workspace storage folder:
Windows: %APPDATA%\Cursor\User\workspaceStorage
Delete the folders inside that are related to the affected project (or delete them all, Cursor will recreate them)
Restart Cursor and open the project again
Also please check:
Does Cursor open normally in another folder or an empty project?
What do the logs show: Help > Toggle Developer Tools > Console tab. Please share a screenshot of any error messages
About exporting and moving chats between machines, try the Cursor Chat Transfer extension:
It lets you export and import chats between workspaces, and they show up right in the Cursor UI. It works on Windows, Mac, and Linux. This should help you move chats to your work laptop.
Hey, thanks for the update. It looks like the workspaceStorage workaround only helps temporarily. That suggests the issue is deeper.
Based on the errors in your screenshots (OTLPExporterError, File Watcher ENOENT/EISDIR, UsageDataService failures), this looks like an extension host issue in large projects. This is a known problem, and the team is working on a fix.
To help the engineers, could you share a bit more info?
Please test:
Open Cursor in an empty folder or a small project. Does it work normally?
What’s the size of the project that breaks (file count, does it include node_modules, .git, or other large folders)?
For diagnostics:
If you can send a chat request before it crashes, please copy the Request ID (top right in chat > Copy Request ID)
I actively work on 2 projects. One is a quite big App (22,524 files and 2,531 folders) which works perfectly so far on Cursor. The other one that has the bug is much smaller (9,579 Files, 1,056 folders including .git-3,671 files and node_modules-5783 files so only 125 files outside of those, includes images)
I never had any issue like this before yesterday when my computer rebooted while I was away (not sure was caused the reboot). When logging back in everything, this is when the problem occured
If I do not send any AI requests, nothing crashes
Around the moment the crash occurs, I get a message on the bottom left saying “Analyzing ‘name_of_file’ and its dependencies”
As I said, my other big project, with 10x more code, is working perfectly on another Cursor window. If I switch folder on the working Cursor window and open the “corrupted” one, the bug starts.
Here are a few request IDs that were affected by the crash (stops the AI answers) :
650ca297-4ead-44f8-81fe-d533085069aa
14a59937-fc7e-418c-b159-bccf1c997ca0
This one I have been able to get some answers by restarting several times (20x) the extensions : 7b16a656-921e-4a7b-9456-86997e722384
The WSL extension allows Cursor to run extensions within the WSL environment, which will be much more performant and lead to fewer extension host crashes. Please install the WSL extension.
After you install the extension, inside a WSL terminal, navigate to your project location, and then run cursor . to launch Cursor using the extension.
