Agent stuck forever

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Suddenly , today I update the newest version ,Then my agent mode stuck forever , it can’t edit any file , what are you doing ?

Steps to Reproduce

Agent mode.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.50 (system setup)
VSCode Version: 1.105.1
Commit: 56f0a83df8e9eb48585fcc4858a9440db4cc7770
Date: 2025-12-06T23:39:52.834Z
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?

Any model can not edit .

Additional Information

My enviorment is windows + wsl , I used this for 3 month , today the new version’s agent crashed.

Does this stop you from using Cursor

Yes - Cursor is unusable

6 Likes

Have you tried using an earlier version e.g. 1.5

Roll back to “Version: 2.0.77 (Universal)”, new curosr version is not working

1 Like

I have the same issue and reverted to 2.0.77 version but the currently freely available GTP-5.1 Codex Max models are unusable with this older version (neither with the latest one, wow).

Specifically, in 2.0.77 version the terminal commands don’t appear/aren’t visible in the agent chat but they can be ran:

image

Cursor’s unstable update cost my patience , every day I will receive an new update-version , I want to switched to Antigravity.

1 Like

I’ve been seeing the same thing and I have a workaround!

Workaround first so you can get back to work: Tell it

Use echo “content” > path.txt or some other terminal command instead of the create file tool, since that doesn’t seem to work’. 

This seems to work on auto at the very least.

Context:
The bug seems to be a desync between the events streamed from the agent and the UI.

Cursor seems to use markdown as the source of truth for timeline events streamed to the UI.
At some point, the ‘Accept/Deny’ button for the create file seems to dissappear from the GUI, resulting in the agent being stuck in the ‘Accept/Deny/suggest other’ as seen in the placeholder of the input.


This is why the agent is ‘stuck’. Its waiting for your confirmation of changes.

This seemed to happen in a recent update that changed the behaviour so that files are not automatically created now. The client/agent seems to think of creating files as a higher permission status or doesn’t reconcile it with the previous one, but there is also no UI functionality to add this command to the allow list.

This seems to happen less frequently when I run it as an admin, but all paths eventually lead to this for me at least.

Try the workaround for now!

Run shows up, so you can continue

Hey, thanks for the report.

This is a known issue with version 2.1.47 on Windows + WSL. The team is already working on a fix.

Temporary workaround - roll back to 2.1.42 or 2.0.77:
Users have confirmed these versions are stable with WSL.

Let me know if the rollback helps.

1 Like

Mate, thanks for your workaround , I roll back to 2.0.77 , it work well right now.

2.0.77 work well for me .

Rollback don’t work for me

Bad luck for you . LOL

2.0.77 doesn’t work even when typing in the chat to use echo “content” > path.txt …
Tried with both auto mode or picked model and the terminal command isn’t visible and fails to execute:

When using the latest version, the Agent is stuck forever so I can’t find a solution at the moment!

This issue seems to be related to Agent Mode keeps asking approval for changes

The latest Cursor update seems to prevent AI agents from creating and editing files in Windows/WSL2 environments.

A workaround shared by @mwz in another thread resolved both issues for me: disable ‘External-file Protection’ in the settings:

Switching off external file edit protection fixed this for me for the short term (Edit: Cursor Settings>Agents tab)

1 Like

Oh, thank you so much. This fixes super annoying “Accept on every change” behavior.

Where can we find previous versions ?
Where is the download link for 2.1.42 ?

1 Like

Found !

1 Like

Hey Dean, this is not a Win+WSL specific issue.

I can confirm the same behavior on Mac since the three quick updates yesterday.
And after some unstable behavior in the planning mode for the past week.

Current state is completely unusable as far as AI support goes. Right now it’s a paid VSCode.
I understand Cursor is rolling some pretty big features now and kudos for the job.
But keeping the core stable while at it, especially for such obvious issue all over the place, is a must.

What’s the ETA for a fix?

System details:
Version: 2.2.17 (Universal)
VSCode Version: 1.105.1
Commit: cf858ca030e9c9a99ea444ec6efcbcfc40bfda70
Date: 2025-12-11T18:30:06.649Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.6.0

The 2.2.20 (Universal) update (darwin/arm64) worked for me.
(Cursor > Check for updates)

@Cursor team, you should really discuss your quality control processes for releasing updates. Their frequence increased but the quality is degrading.

1 Like

Yes , I have to update cursor 3 times a day , I think it is a little annoying.