Is Cursor IDE an example of AI failure?

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

For some reason Cursor stops creating and writing files.

I have to manually type “continue”. I say “for some reason” because it is entirely opaque. If I ask Cursor “why have you stopped” then it ignores the question and just continues. If I search the web for similar issues I see the forums awash with users struggling with Cursor.

There is never any feedback from the developers and there is no guidance on how to get Cursor to behave.

With traditional software debugging was pretty straight-forward. You understood the state of the application and could trace a path that lead to the problem state. With Cursor it seems that there is this great mystery - it has stopped working and nobody knows why. The developers don’t seem to care, there is never feedback on the forums.

It’s so opaque that I can’t even say which agent Cursor is currently using. I can’t determine if there are any settings that make it pause (without any UI buttons) and stop working.

Yet still the Cursor IDE rushes forwards to deliver new features, even while users struggle with bugs that make the product unusable.

This seems, to me, to be the hallmark of AI driven engineering. Move fast, but when stuff breaks there is no way to debug it.

Steps to Reproduce

Well that’s the problem. I’m just asking Cursor a prompt “implement this mapping and add avatar support to NPCs”. You don’t even tell me what agent I’m using. It seems impossible to reproduce and I’m betting you don’t even bother trying. Why else are forums full of ignored bug reports?

Expected Behavior

I expect Cursor to write files and then ask me to review and accept them at the end.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.50 (user 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.26100

For AI issues: which model did you use?

Auto

For AI issues: add Request ID with privacy disabled

3179c4fe-a635-4b16-83cc-9ee9f3341150

Does this stop you from using Cursor

Yes - Cursor is unusable

5 Likes

Version: 2.1.50
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: Linux x64 6.8.0-88-generic

Same here, just stop when i type continue dont looks like resume the agent loop and sometimes just finish in middle a refactor when i ask to continue

Try not to use Auto.

1 Like

Hey, thanks for the report. We’re seeing a few similar issues on 2.1.50. To unblock yourself for now:

  • Try not using Auto - pick a specific model and restart the agent
  • Before the next command, explicitly Accept or Reject all current diffs
  • Temporarily roll back to the stable version 2.1.42: Download · Cursor
  • Restart Cursor

Related threads and workarounds:

The team is already working on a fix and your case can help. Thanks!

1 Like

FYI: Seems the download link now points to 2.1.50

This also may be of help: When I restarted the plan in agent mode cursor was out of focus and the pop-up said awaiting approval for edits. I can see this when I switch to agent view. See image.

Was able to get it to realize it was stuck and it went off using power-shell to finish the task. Interesting. Seems it lost the tool-call ability to save files and got stuck. It wasn’t pretty but it did get the task done!

CHAT ID: ffd22696-5ead-4bb7-835c-4c0e907a216e

1 Like

That continue option stems back as far as 1.4, todays version of Cursor is just the old version patched with bugs. I wish they would do a complete rewrite.

1 Like

1.7 and 2.0 is pretty nice

Thanks for the response. The link you gave is broken and I don’t see a way to rollback.

I am holding back updating my work machine version until there is a stable release.

Is there a page that indicates whether an update is safe to apply?

1 Like

It looks more like it’s not seeing the out out form terminal and that a bug that comes Long every other date. I maybe wrong tho. If it it stopping in terminal you can open the terminal and press enter a few times and it fixes it however it will some times not see the output form the terminal to avoid that issue you can press up then re run the command.

Over all cursor is the best ide with AI.

Probably going back to 1.3 will fix the issues :slight_smile:

You don’t see the roll back button option per convo? The send prompt button turns into a type of revert button. It reverts the codebase back to this point in time. I noticed this system isn’t always functional and suggest duplicating the codebase local and storing in GitHub (but I’m sure you already do that)

this forum is likely the best place for understanding what versions are best. Also don’t expect new software to perfect a codebase before shipping. Imagine they are building large Trojan horses and inspection inside is most beneficial. Plus, never updating just because a pop suggests you become a beta tester to a new version! Always wait.

I have found that problems such as this are almost always the result of a bad plug-in. Launch cursor with plug-ins disabled on startup. If your problem goes away, then you know what the issue is. You just have to go one by one through your plug-ins until you figure out which one is causing the hangup.