When opening the project in Cursor 3 it does not load initially saying “taking a while”. When closing and reopening the window the project is opened then
Steps to Reproduce
Just try to open your project in Cursor 3 for the very first time
Hey, thanks for the report. That symptom looks familiar. It matches a known issue where Cursor can hang on startup while restoring the git diff tab in Source Control. It’s more noticeable on WSL because the remote session initializes more slowly. The second time the window opens fine because that problematic tab doesn’t get restored again.
To confirm it’s the same case, quick question: before you closed the window the first time, did you have any Source Control or git diff file open, like you were viewing a file’s changes from the Source Control panel? If yes, that’s an exact match.
We’re tracking this on our side, but I can’t share an ETA yet. Temporary workaround: before closing Cursor, close any diff tabs opened from Source Control. Then the next launch shouldn’t hang.
Thanks for confirming. If there was no Source Control or diff tab open, it might not be the same restore hang, but it could still be a similar startup flow with a different tab type.
A couple of questions to narrow it down:
When the project hangs on first open, what tabs or files, if any, were restored from the previous session? Anything notable like large files, remote paths, image previews, or notebooks?
Does it hang on every first open, or only sometimes?
When it gets stuck on taking a while, can you open Developer Tools via Help > Toggle Developer Tools, then go to the Console tab and share anything that looks like an error or a repeating message?
Does it still hang if you open Cursor in a fresh window first with no workspace, then use File > Open Folder to open the project?
Also, just to rule things out, does the same project open fine in Cursor directly on Windows without WSL, or have you only tested via WSL?
We have merged a fix and are cherry-picking it back to 3.6. Please try again in a day or two (3.6.35+, not available yet) and let us know if the issue persists.