Windows 11 x64
Cursor 3.14.7
The application opens directly to “Something went wrong.”
Renderer log: [unauthenticated] No authorization header found.
I already performed a clean reinstall, reset globalStorage, launched with
–disable-extensions and --disable-gpu, and tested a different network/hotspot.
Hey, thanks for the detailed report. What you’re seeing isn’t caused by your setup, so reinstalling, resetting globalStorage, using --disable-extensions or --disable-gpu, or switching networks won’t help.
On the current stable build 3.14.7, the client sometimes starts sending requests before the auth token is attached. Those requests go out without the Authorization header and get rejected with No authorization header found. In your case, that makes the app fall into the “Something went wrong” screen right at startup.
What you can do right now:
On the error screen, click Reload Window. Sometimes it doesn’t work the first time. If the window opens, you can also repeat it via the Command Palette Ctrl+Shift+P then Developer: Reload Window.
If the app won’t open reliably, a workaround is to use Cursor CLI. It uses a different path and doesn’t touch login Cursor CLI | Cursor Docs
Important: updating within the 3.14 line won’t fix this, and I don’t recommend chasing a separate pre-release build just for it. The fix is already in newer builds that haven’t reached the stable channel yet. I’ll reply here when a stable update is available.
If Reload Window doesn’t help even for a couple of seconds, tell me and share the exact version from Cursor > About Cursor.