Writing long prompts and accidentally hitting Enter

While writing long prompts in cursor,

Sometimes I accidentally hit just “Enter” and it sends the half-written prompt to cursor.

It should have a mode where pressing Enter just opens a new line instead of sending the prompt.

Is this already there? Or is there any workaround to this?

1 Like

Hey, something like cmd/ctrl + enter to submit the request?

1 Like

I do that already. But sometimes when I am typing long prompts, the muscle memory kicks in and I end up pressing just Enter.

2 Likes

Had exactly the same issue in 0.48.7. Used to submit Chat prompt with CMD Enter but with Enter it submitted. Yes i can do Shift Enter for newline but its not intuitive.

Wasnt CMD Enter default? its default for all forms on the web and many applications.

CMD Enter may have been conflicting with Approve but that moved to CMD SHIFT Enter so no conflict anymore.

1 Like

in an odd weird way - there are times when I have sub-optimaly hit ENTER and submitted my half-baked prompt and gotten SUPRISING results such that it actually infered the rest of my intent.

So just know that there is a skill to be had which is to throw the bot partial info and have it “figure the things out” sort of prompting…

Kind of like a merge btwn vibe coding and direct coding

1 Like

I wonder if you could make a vs-code extention that has a color gradient for your prompt such that as you type your prompt out it can do an eval_as_you_go sort of thing so that youre vibing in realtime with the bot as you type…