After opening a project Cursor unresponsive

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I was trying out new cloud agents.
At some point Cursor hanged and became unresponsive.
Now each time I open project it hangs.

Steps to Reproduce

I open specific project, other projects work well.
I have a few cloud agents opened in agents list - I suspect it has something to do with this,

Expected Behavior

I can use Cursor

Screenshots / Screen Recordings

Screenshot 2026-03-02 at 01.40.50.png
Screenshot 2026-03-02 at 01.40.50.png794×810 54.1 KB

Operating System

MacOS

Version Information

Version: 2.5.26
VSCode Version: 1.105.1
Commit: 7d96c2a03bb088ad367615e9da1a3fe20fbbc6a0
Date: 2026-02-26T04:57:56.825Z
Build Type: Stable
Release Track: Early Access
Electron: 39.4.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.3.0

Additional Information

I am not sure where to find any log files I can attach.
I can provide as needed, along with the full project as well.

Does this stop you from using Cursor

Yes - Cursor is unusable

3

Hey, it looks like the freeze is caused by this project’s workspace state. It’s probably because when Cursor opens, it tries to restore cloud agent sessions, and something in that state is blocking the main thread.

The fastest fix is to clear the workspace state for just this project:

  1. Fully quit Cursor
  2. Open ~/Library/Application Support/Cursor/User/workspaceStorage/
  3. Inside, you’ll see folders with random hashes. Each one has a workspace.json file. Open them to find the one that matches the path to your problem project
  4. Delete that folder (or rename it as a backup)
  5. Open the project again

This will reset the workspace state (open tabs, cloud agent sessions, etc.) only for this project. Everything else will stay unchanged.

If you want to be extra safe, you can launch Cursor from Terminal with:

cursor --disable-extensions /path/to/your/project

But I doubt it’s extensions. It’s more likely the cloud agent state.

Can you share how many cloud agents were open in this project, and roughly how long they were running? That info will help with debugging.

Let me know if resetting the workspace helped.

4

截屏2026-03-02 16.58.36
截屏2026-03-02 16.58.362072×1324 86.3 KB

I’m encountering the same problem; the workspace is now completely inaccessible, and the agent cannot be deleted. Below is my environment information. I tried uninstalling the cursor and restarting the installation, but it still doesn’t work. It seems that reloading the agent takes a long time, and the system doesn’t have good fault tolerance. @deanrie
Version: 2.5.26
VSCode Version: 1.105.1
Commit: 7d96c2a03bb088ad367615e9da1a3fe20fbbc6a0
Date: 2026-02-26T04:57:56.825Z
Build Type: Stable
Release Track: Default
Electron: 39.4.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.2.0

5

I waited a long time for the current agent, about 5 minutes, before it started responding. At this point, I created a new agent, and then worked in the new agent window within the same workspace. However, if I continued to interact with the old agent, the connection would remain stuck.
@deanrie

6

I’ve already re-created project from scratch and all is fine now - I guess we need to wait a bit until cloud agents are polished out. My old workspace is still there in case I can help with any info to help investigate this.

I had 3 or 4 cloud agents, and the last one, which probably caused the issue, is the one that sets up the cloud env for you.

1 Like