Cursor is not about vibe coding. Vibe coding means you don't care about the AI's code output as long as it works. Cursor is all about efficiently reviewing the AI-proposed changes and hitting Tab only when you approve them. Much of the editing process is hitting Esc because the proposed change is not good.
I know this is a meta point but I'm pretty sure vibe coding is just an X meme that means whatever the poster intends. I'm not sure you can say vibe coding does or doesn't care about relative quality
Yeah, I'm afraid "vibe coding" is a term that quickly lost its meaning because everyone was using it to mean different things.
Some people use it to mean using AI for writing code in general. I've preferred for it to mean when someone who doesn't know how to code uses AI to write code and doesn't understand the output.
Almost, but not quite. As per Karpathy's definition [0], it's not about not knowing to code (he obviously does), but rather not caring -
"fully give in to the vibes" and "forget that the code even exists". So the closest implementation to this ideal would probably be something like lovable.dev, that fully hides the code from you, because if you can't resist the need to look at the code, you're not fully "vibing".
Agreed, that's how you'll have much more success using it. Basically, I ask it to write 4-10 lines at a time, if the lines are too many for me to comfortably review, I reject the change and ask more specifically.
there is essentially no difference if you give the agent total control in cursor, you can code entirely via prompt without ever touching the code after you create a workspace.
that is to say I can't think of any greater support of vibe-coding , you can open up a chat prompt and have at it.
