Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
Cursor is not loading source control, terminal, extensions when opening application.
I have to try closing and reopening the app a few times. It will eventually work. One time it took 2 retries to work. Another time it didn’t fully load cursor until the 3rd attempt.
Steps to Reproduce
Open cursor
Expected Behavior
Everything should load.
Screenshots / Screen Recordings
Operating System
MacOS
Version Information
Version: 3.2.11 (Universal)
VSCode Version: 1.105.1
Commit: e9ee1339915a927dfb2df4a836dd9c8337e17cc0
Date: 2026-04-24T14:36:47.933Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 24.6.0
Does this stop you from using Cursor
Sometimes - I can sometimes use Cursor
Hi @something_something
This is a known issue. The Extension Host sometimes fails to finish initializing on startup, which causes source control, terminal, and extensions to all fail to load. Our team is actively investigating it.
A workaround that has helped others is deleting the workspaceStorage folder – Cursor will regenerate it automatically. On macOS, the path is:
~/Library/Application Support/Cursor/User/workspaceStorage
You may also find this related thread helpful: Nothing initialises include source control providers, output, extensions etc
Please fix this, it is extremely annoying to have to find and delete a folder every single time I want to use cursor. @mohitjain
I hear you. Having to do that every time you open Cursor is not acceptable.
A quicker alternative that avoids folder deletion entirely: press Cmd+Shift+P and run Developer: Reload Window. This restarts the Extension Host and usually brings everything back in a few seconds, without quitting Cursor or touching any folders.
On the permanent fix: this is a high-priority issue our team is actively working on. I don’t have an ETA to share yet, but I’ll follow up here when it ships.
Would this explain why on startup half the time the “npm scripts” panel does not load? I find I have to restart Cursor after startup frequently to get this panel to appear.
I’m on Version: 3.2.21 (Universal)
and it’s not loading.
I have tried “Developer: Reload Window” and it doesn’t work
The only way I can get cursor to open now is if I delete
~/Library/Application Support/Cursor/User/workspaceStorage
every time before I try to open it.
Is this being worked on?
@anthonyleeper - Yes, most likely. The npm scripts panel is loaded by an extension, and the same Extension Host initialization issue can prevent it from loading on startup. The same workaround applies: press Cmd+Shift+P and run Developer: Reload Window. A permanent fix is coming in a near-term update.
@something_something - Sorry this is getting worse for you. If Reload Window stopped helping on 3.2.21, the workspaceStorage deletion is unfortunately the most reliable workaround right now.
Our engineering team has shipped multiple Extension Host stability improvements that are in testing internally and will reach stable in the next update. Once that lands, this should be resolved. I’ll follow up here when it’s available.
