Severe Issues After Latest Update: Agents Not Loading, Frequent Crashes

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Hi everyone,

since Cursor updated last night, I am experiencing serious problems that make the application barely usable.

After the update, I was forced to log in again. Since then, all my old agents are no longer accessible. When I click on an existing agent, it starts loading, takes a long time, and then nothing happens. The agent never opens.

I tried working around this by creating new agents, which initially worked. However, since then, the application has started to crash very frequently. The crashes occur during normal usage and are not tied to any specific heavy operation.

So in summary, since the update:

I had to log in again unexpectedly

Existing agents no longer open (endless loading, no error)

New agents can be created, but

Cursor now crashes very often, making productive work impossible

This all started after the latest update, and I did not have these issues before.

I am posting this here to see:

if others are experiencing the same behavior

and to make the Cursor team aware that this update seems to have introduced serious regressions

If anyone has found a workaround or has more information, I would appreciate it.

Thanks.

Steps to Reproduce

Update Cursor to the latest version (update installed overnight).

Start Cursor.

Cursor prompts for login again.

Log in with the existing account.

Try to open an existing agent created before the update.

Observe: agent shows loading state for an extended time and never opens.

Create a new agent and start working in it.

After a short period of normal usage, Cursor crashes unexpectedly.

Restart Cursor and repeat steps 5–8.

Expected Behavior

Cursor should not require re-login after an update unless explicitly necessary.
All existing agents and their histories should remain available after an update.
Clicking on an existing agent should open it within a reasonable time.
The application should remain stable during normal usage without frequent crashes.
Updates should not cause loss of access to user data or workspace state.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.3.21 (user setup)
VSCode Version: 1.105.1
Commit: 68e0a0385b87408d050869ea543e3778ad53f780
Date: 2026-01-02T23:46:13.381Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

gpt-5.2

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

2

i can confirm after i updated to 3.2.20 mcp servers take around 5 minutes to load, sometimes never load, i have to manually disable and enable them one by one in settings

3

Hey, thanks for the report.

This is a known issue on Windows: checkpoint data can get corrupted during chat or agent migration. Version 2.3 includes fixes for this, but it looks like it can still happen for you.

To debug, we’ll need logs:

  • Help → Toggle Developer Tools → Console
  • Try opening the agent that won’t load
  • Send the errors from Console (especially [composer] or [data_loss])

Workarounds for now:

  • Try updating to the latest stable version (Early Access is in Cursor Settings → Beta)
  • For crashes, run cursor --disable-extensions to check if it’s extension-related
  • Export important chats (three dots → Export transcript)

About MCP servers (@liquefy): try reloading the window after starting Cursor, or disable and re-enable MCP servers one by one.

Related report: Some chats fail to load or open

Send the logs and we’ll dig in further.

4

workbench.desktop.main.js:15694 Error getting git root Error: Failed to execute git

workbench.desktop.main.js:13857 [composer] Error checking git status for auto-accepting diffs: Error: Failed to execute git

workbench.desktop.main.js:15694 Error getting git root Error: Failed to execute git

workbench.desktop.main.js:13854 [composer] No composer data handle found [handleDeselectingComposer]

workbench.desktop.main.js:13854 [composer] No composer data handle found [handleDeselectingComposer]

workbench.desktop.main.js:13854 [composer] No composer data handle found [handleDeselectingComposer]

workbench.desktop.main.js:13854 [composer] No composer data handle found [handleDeselectingComposer]

5

Thanks for the logs. I see two separate issues:

  1. Git errors
    The “Failed to execute git” error means Cursor can’t find git.exe. Please check:
  • Is Git installed on Windows
  • Is the path to git.exe added to the system PATH environment variable
  • Restart Cursor after installing Git

  1. Composer data handle errors
    These are warnings and don’t mean data loss (unlike the [data_loss] tag). Important: your logs do NOT show checkpoint corruption like in Some chats fail to load or open

  2. Frequent crashes
    Please try:

  • Run cursor --disable-extensions from the command line to see if it’s related to extensions
  • Press CTRL+Shift+P > Developer: Open Process Explorer to check which process is using resources

Let me know what you find after checking Git and testing crashes with extensions disabled.

6

This is not possible because the chat no longer opens. Exporting is only possible when the chat is open.

7

image
image623×246 8.04 KB

I have attached a screenshot of today’s crash. This is the third time this has happened in a row.

8

Git is installed all the time. Where can i do this:

Is the path to git.exe added to the system PATH environment variable

On my PowerShell I already commit the projects all the time.

9

If Git works in PowerShell, your PATH is set up correctly. Cursor sometimes uses a different PATH.

Try this:

  • Fully close Cursor
  • Open PowerShell and run: cursor
  • This will launch Cursor with the same PATH as PowerShell

If the Git issue goes away, it means Cursor is starting with a different environment. In that case, restart Windows to refresh system variables.

About the crashes, were you able to test cursor --disable-extensions?

10

Yes I am runnig it now with disable-extensions. I will see and report if it’s better. Ok, I will try the rest you said.

1 Like
11

You can check if the Git path is added to the system PATH environment variable by right-clicking on ‘This PC’ (or ‘Computer’), selecting ‘Properties’, then ‘Advanced system settings’, ‘Environment Variables’. Scroll down to ‘Path’ under ‘System Variables’ and check if ‘C:\Program Files\Git\bin’ (or wherever you installed Git) is listed. That should give you a clear answer.

1 Like
12

image
image716×817 49.3 KB

I checked it and C:\Program Files\Git\cmd was alredy there so I have added C:\Program Files\Git\bin. After restart of the computer the problem is still there:

image
image787×760 67.5 KB

1 Like
13

But today he asked me to reconnect to Git, which I did successfully. After that, I think Cursor started crashing.

15

I ran cursor --disable-extensions from the command line, but this did not reduce the crashes. Cursor still crashes regularly and interrupts my work.

16

Thanks for the screenshot with the logs.

The telemetry errors (OTLPExporterError, “unauthenticated team member”) are Cursor internal metrics. It’s safe to ignore them, and they don’t affect how Cursor works.

The main issue is the crashes. This is a known problem on Windows. A few things to check:

  1. MCP servers: In Cursor Settings, search for “MCP”. If you have any servers set up, especially GitHub or Atlassian, try disabling them and restarting Cursor.

  2. Windows Update: One user reported that rolling back update KB5068861 fixed the freezes. Please check: Settings > Windows Update > Update history. Is it installed?

  3. Before the next crash, open CTRL+Shift+P > Developer: Open Process Explorer and take a screenshot. This will help us see which process is causing the issue.

Also, a note from a similar thread: VS Code also freezes in the same way on some systems, which may point to a Windows or driver issue.

17
  • See above.
1 Like
18

Screenshot after the crash.

image
image1917×520 24.6 KB

19

Thanks for the detailed Process Explorer screenshot.

I can see that extensionHost is using 422 MB of memory. This can point to an extension issue or a memory leak. A few extra steps to try:

  • Extension Monitor: Press Ctrl+Shift+P → Developer: Open Extension Monitor and check which extensions use the most resources. Try disabling the heaviest ones.
  • Console logs during the crash: Help → Toggle Developer Tools → Console. When the next crash happens, copy all Console messages, especially anything tagged [composer] or [electron].
  • Clean workspace: Try opening an empty folder and use Cursor for 10 to 15 minutes. If it doesn’t crash, the issue may be tied to a specific project.
  • Temporary workaround: If the crashes make it impossible to work, consider rolling back to version 2.2.x for now. In Settings → Beta, you can turn off Early Access.

About agents not loading, that’s a known issue with checkpoint corruption in version 2.3. The team is working on a fix.

Let me know what you find in Extension Monitor and the Console logs.

20

I appreciate the suggestions, but I need to be very clear.

I do not have the time to continuously investigate the root cause on my side. In its current state, it is simply not possible to work productively. When I have larger or more complex chat requests, Cursor crashes almost every time. This is not an edge case, it is a recurring and blocking issue.

Regarding extensions: I already tested running Cursor with extensions disabled, and the crashes still occur. This strongly suggests that extensions are not the root cause.

I would like to install an older, stable version as a temporary workaround. However, in Update Access I only see the options Default, Early Access, and Nightly. When I switch to Default, it says “No updates available”.

Can you please clarify:

  • How can I roll back to a previous stable version?

  • Is there an official download or supported way to restore an older version?

At this point, I need a practical solution to continue working. Detailed local debugging is not feasible for me right now.

I would appreciate clear guidance on how to proceed.

21

I want to provide a quick update.

I reinstalled version 2.3.20, and at the moment it appears that the crash issue may be resolved. Since reinstalling this version, Cursor has not crashed so far.

I will continue monitoring this, but for now the application seems stable again.

I will report back if the crashes reoccur.