Cursor intermittently loses all source control integration after the system has been shut down for an extended period. The Source Control panel shows:
“No source control providers registered”
The issue is resolved by deleting the workspaceStorage folder, indicating corrupted or invalid workspace state.
Steps to Reproduce
Open a project with a Git/Bitbucket repository in Cursor
Shut down the computer for an extended period (e.g., overnight)
Restart the system and reopen Cursor
Open the Source Control tab
Expected Behavior
The Git repository should be detected and source control features should be available.
Operating System
Windows 10/11
MacOS
Linux
Version Information
Observed since at least version 2.6.22 through 3.1.17
Hey, thanks for the report. This is a known issue. The Extension Host doesn’t initialize after a long idle period, so the built-in Git extension doesn’t start and the SCM view shows “No source control providers registered”. Deleting workspaceStorage is a known workaround.
We’re tracking this internally, but there’s no ETA for a fix yet. To add your case to the report, please send logs:
Command Palette Ctrl+Shift+P > Developer: Open Logs Folder
Zip and attach it here. We need the Window, Main, and Extension Host sections
Also helpful to know:
Your OS. Your report lists all three, so please confirm which one you reproduced this on
Next time you hit the bug before deleting workspaceStorage, grab logs right away. That’s the most useful
When I open some of my projects, Cursor does not work.
The IDE opens, but it claims that “No source control providers registered”, I can’t see the terminals and agent is unreachable. When I try any prompt it keeps loading for some time and then times out on “Agent Execution Timed Out”. It offers to “Reload the Window” but it usually doesn’t work (sometimes, very randomly it does help).
Then sometimes it helps to restart Cursor several times, or trying to open working projects (which is also random) and then re-opening the ones that faced this issue initially. But these gymnastics are unpleasant. I need to open the project and start working.
Steps to Reproduce
Just open the Cursor IDE with the last project it remembers, or open any other project that faces this issue (most do).
Expected Behavior
I open the IDE with the last project, or I open any of the project and it just works. I can see the git history, the terminals and agents are responsive.
If codex is also running close both then only start Cursor, fixxed for me after many restart attempts on Cursor only. Have a great day.
Edit: AI Answer below
Summary
If Codex and Cursor both use VS Code-style workspace state, extensions, Git watchers, or shared workspace metadata, closing both and starting only Cursor can help because:
Codex may keep file watchers or Git processes alive.
Cursor may reopen with stale workspace state after sleep/shutdown.
Both tools may read/write related workspace cache/state.
Long shutdown/sleep can leave invalid extension host or Git provider state.
Starting Cursor alone forces a cleaner extension/Git initialization path.
But this is probably a workaround, not the root fix.
Because deleting workspaceStorage fixes it, the real issue is likely corrupted/stale Cursor workspace state, not the repository itself.
If Git appears, then Codex/shared state or lingering processes may contribute. If it still fails, the bug is inside Cursor workspace storage / Git extension activation.
Experienced the same issue today on macOS 26.3.1 (a) (25D771280a), Cursor Version 3.2.16 (Universal), with Codex enabled. Once Codex was completely uninstalled from my computer and Cursor was restarted, the IDE started working as usual. Before that, it was throwing the same errors other users mentioned in the thread.
Hey, I get it. If it crashes on every launch, that really blocks you from getting work done. We’re tracking the issue, but to add your case to the report we need a bit more info:
Your OS and Cursor version: Help > About
Do you have the Codex extension installed, or any other AI extensions? A few users in this thread said disabling Codex fixed it:
Logs from when it happens, before deleting workspaceStorage: Ctrl+Shift+P > Developer: Open Logs Folder, zip it and attach it here. We need the Window, Main, and Extension Host sections
Since it happens every time, these logs are extra useful and should help the team pin down the root cause.
One more request: before deleting workspaceStorage, please collect logs Ctrl+Shift+P > Developer: Open Logs Folder, zip them, and attach them here. We need the Window, Main, and Extension Host sections. After clearing, it’s harder to reproduce the issue, and the logs really help the team find the root cause.