Terminal + Version Control doesn’t load still

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor still not loading cleanly - needing workspacestorage cleared out

Steps to Reproduce

Terminal + Version Control doesn't load is now closed which is disappointing. This issue is still happening, and I was told a fix was coming so I didn’t keep replying to the thread. But it’s getting beyond a joke that every few times I start cursor It won’d load properly and I have to clear out some of my workplacestorage.

Expected Behavior

Cursor opens everytime and keeps settings

Operating System

MacOS

Version Information

Version: 3.7.21
VS Code Extension API: 1.105.1
Commit: 517f696d8ab6c53eb04fbfdaae705cd146bf3460
Date: 2026-06-07T21:46:09.237Z
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
xterm.js: 6.1.0-beta.256
OS: Darwin arm64 25.5.0

For AI issues: which model did you use?

Auto

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Hey @Ptorrsmith_JAVLN,
That’s our forum’s auto-close kicking in, not us dropping the issue, and I get why it was frustrating after being told a fix was on the way.

This exact startup hang (Terminal and Source Control never initializing, only cleared by wiping/moving workspaceStorage) was tracked down and fixed. The catch is that the fix landed in a build after the one you’re running. Your About panel shows 3.7.21, built June 7. The fix went out shortly after that, so your install never picked it up. Another user hitting the same bug confirmed it was resolved once they updated.

The reason you’re pinned to that June build is almost certainly the update.mode change from the earlier thread. Setting it to manual/none stopped the auto-updates, which unfortunately also kept you on the pre-fix version. And to reassure you on the worry from before: the update itself won’t retrigger this. We confirmed earlier that it’s stale layout state in state.vscdb, not the update process, so getting current is safe here.

To get onto the fixed build:

  1. Re-enable updates: Cmd+Shift+P → Preferences: Open User Settings (JSON), then set "update.mode": "default" (or just remove the line you added earlier).
  2. Update now: Cmd+Shift+P → Attempt Update, then fully quit with Cmd+Q (not Reload Window) and reopen.
  3. Check Cursor → About Cursor: anything 3.7.35 or newer has the fix (you’re on 3.7.21).

If it hangs one more time before you get updated, the cleaner stopgap (instead of wiping all of workspaceStorage) is to fully quit Cursor and move aside just three files in that workspace’s hashed folder: state.vscdb, state.vscdb-shm, and state.vscdb-wal. Back them up rather than deleting, so you can restore if needed. That resets only the broken layout state, not your settings.

Once you’re on the latest, give it a few restarts and let me know if it holds. If it somehow still recurs on the current build, reply here and I’ll dig into fresh logs with you.

Thanks Mohit for the clear explanation.

I’ve reset updates to default and am updating now.

Thanks for the efforts.

Peter