Kindof in the middle of my workflow problems started popping up, and I realized it was because Cursor just updated.
Firstly, any codeblock that is typed out in chat or composer has the first character of each line deleted. I have no idea why this is happening, but only started after the update.
Secondly, there are a number of times that now… when attempting to apply codeblock changes, it will not prompt me to accept the changes after it has finished applying them. This forces me to go through and click “approve” on each line change in the editor window.
Still working with the new update. Will report new issues as they occur.
Example of the issue where it randomly cuts off the first character in code blocks. Extremely annoying. Didn’t even notice it at first until I started getting random errors that I had to debug.
Also another issue is that in some chats, generation will now hang indefinitely. I think there is some kind of markdown or syntax issue that is corrupting entire chats or something. Not sure. If I start a new chat, works fine. However certain chats can now no longer continue conversations.
Only started happening today after the new update.
I can confirm this as well—I’ve had a similar experience, and unfortunately, I’m not very happy with the agent so far. For me, the biggest downgrade is the removal of the “Add Files to Composer” option that was previously available in the file explorer, allowing multiple files to be added to the context at once. Now, having to add everything one by one is incredibly tedious and unnecessarily complicates the workflow.
In general, the handling of context—both adding and dismissing it—could have been addressed in a much more elegant way. As it stands, the current system feels clunky and impractical, especially for larger projects involving multiple files.
Is there a way for us to roll back to the previous version? Not sure if that is something we’re able to do. I really had a lot of work to get done today lol it would be nice if I could disable auto-updates, or roll-back if issues like this occur. This is really going to get in the way of me completing my work this Monday
This is also interesting. I’ll use my standard React debugger when actively authoring a component or route integration, then Cursor is pretty good at applying my debug pattern when I need it on demand instead
eg.
Navigation Debugging
Enable navigation debugging in the browser console:
debugConfig.enable("navigation");
It’s a pretty fast change.
The issues is that now I get a pretty long hang. I get it, I just told it to read my whole app for context. Eventually it does work.
But some kind of progress indicator would be nice so that I know the whole thing hasn’t crashed. Otherwise I sit on “Long File Details” for, well, a while, with no indication of what is happening. If I wanted that experience I’d go talk to my terminal (which Cursor also makes awkward since I don’t get the animated cursor block to indicate something is happening, vs the mac terminal where I do)
Guys I’m going to be honest this update has basically nuked Cursor for me, and made it essentially unusable. It is now generating more bugs than actual working code. I can’t even use the features that make Cursor what it is anymore.
