In the screenshot above, at first it wrote a Bash file (which is totally fine for me), but then it started suggesting other options. In the end, it even created a start.sh file, even though I didn’t need it.
Ps: This is just a basic example. I also experienced cases where it changed the file three times and ended up implementing all three solutions in the same code.
I believe if Cursor allowed us to choose which option we want to proceed with and then made the necessary implementation, it would be awesome.
It doesn’t run those options unless you hit run or apply.
unless you are in “yolo” mode or autorun or whatever they call it nowadays, Cursor does not make a single change to your actual codebase unless you tell it to. And it doesn’t force you to make all or nothing changes.
i brought up vibe coding because you seem new to cursor, because you took a picture of the chat menu, and not your codebase as well. The screenshot you show does not show that cursor actually made any change, it just shows that it suggested changes.
I did NOT say that it runs the Bash commands automatically. YOLO mode does that — it runs commands automatically.
As I said there, this is just a basic example where I wanted to express myself.
When three options exist in the same file, it implements all three options consecutively.
Why would I share my codebase at this point? I’m not facing any issues with my code. I’m trying to explain the problem I face with Cursor and make suggestions to improve it. This has nothing to do with my codebase in this example.
PS: I am neither vibe coding nor new to Cursor. Also, not only beginners vibe code. I would recommend understanding what the term vibe coding actually means.
PS2: You’re probably using Manual mode. You can switch by clicking Manual mode (in your case) and then clicking Agent.
