Why is everything in Cursor broken?

Cursing at Cursor:

  1. Their support form won’t submit
  2. Agent chat won’t submit
  3. CLI Terminal doesn’t work
  4. Their AI support bot tries the classic approach of blame shifting to network issues, but that’s irrelevant based on their web form not working via my Mac, and their app not working on my Win VPS.
  5. It seems Cursor’s ads are a far cry from the actually experience: you can’t even do anything in 3 hours, let alone submit a chat, support ticket, add DeepSeek, anything to make progress. They should rename to Toast. Does anybody work there or know how to use Cursor to make it work? Apparently Cursor doesn’t even work for Cursor :confused:

Cursor should use Cursor to make Cursor work properly :confused:

Claude solved Cursor’s own problems:

Got it. Found the real error:

GlassWorkbench startup failed
Illegal argument: contextkey.setConstant(k, v) invoked with already set constant k
That’s Cursor’s chat workbench crashing on startup — in every single window (wb1 through wb6, one per attempt). The input field renders, but the submit handler never registers. So “yo” goes nowhere, spinner forever. Classic.

This is a corrupted user-state issue, usually caused by version upgrades leaving stale data (or a misbehaving extension registering twice). Let me check which.

Read a file, ran a command
Classic Cursor bug — happens in their own workbench.desktop.main.js. Likely cause: stale user-state from a prior version colliding with the current one (note the warning Missing property “rpcFileLoggerFolder”… Please add a migration if necessary — they shipped a version without migrating old state).

Ran
List globalStorage contents
Bash
$ ls “$APPDATA/Cursor/User/globalStorage/” 2>&1 | head -20
state.vscdb
state.vscdb-shm
state.vscdb-wal
state.vscdb.backup
storage.json
Plan: kill Cursor, rename globalStorage + workspaceStorage to .bak (reversible), relaunch. Auth lives in Windows Credential Manager so you shouldn’t need to re-login, and settings.json is preserved. Going:

Ran 3 commands
Cursor’s up with clean state. Give it a sec to finish loading, then try “yo” again. If it works, we’ll delete the .bak dirs. If it doesn’t, I’ll restore them and we try nuclear option (rename the whole %APPDATA%\Cursor dir — that one costs you a re-login but fixes anything state-related).

ah it works now! probably because Cursor was bugging me about updates not available in user-scoped state, so Gemini told me to uninstall it then install the other version, so i did. Man… Cursor should really use Cursor to make Cursor better :smiley:

Ha, yeah — that classic uninstall->reinstall-different-variant shuffle is exactly what causes these state collisions. New binary, old globalStorage, context keys fighting for the same slot. Your .bak-20260418 dirs are at %APPDATA%\Cursor\User\ — safe to delete whenever (6MB total), or leave as a rollback for a day.

And yeah… dogfooding is a journey.

Hey @Nickth,
Glad you got this sorted. You ran into a known edge case – switching between the user-scoped and system install of Cursor can leave behind stale state in globalStorage, which causes the chat workbench to crash on startup. The input field renders but the submit handler never registers, so it looks like everything is frozen.

The fix you found (renaming globalStorage and workspaceStorage to .bak and relaunching) is exactly right. For anyone else who hits this after switching install types:

  1. Close Cursor completely

  2. Navigate to %APPDATA%\Cursor\User\

  3. Rename globalStorage and workspaceStorage (adding .bak so you can roll back)

  4. Relaunch Cursor

Settings and auth are preserved – only cached state resets.

One note on tone – we genuinely want feedback and criticism, which is exactly why this forum is public. Bug reports, frustration, sharp edges in the product – all fair game and genuinely useful to us. That said, we do ask folks to keep things constructive and in line with our community guidelines. Framing like “Does anybody work there” and “rename to Toast” crosses into territory that doesn’t help us help you, and can set a tone that discourages others from participating. The more specific and direct the feedback, the faster we can act on it.

Sorry about the rough first experience. Let us know if anything else comes up!