Suggest to add settings option for choose "Enter" key behavior

[Genymus]

I would like to suggest to create a settings option to allow user to select the behavior of Copilot when the "Enter" key (in the keyboard) is pressed.
Currently, pressing "Enter" send the prompt to Copilot, and if user need a new line, the only way is pressing Shift + Enter.
I suggest to propose to the user two choice:

1. Pressing Enter send the prompt to Copilot;
2. Pressing Enter create a newline. To send prompt, user have to press the UI "send" button

Personally, often I forget to press shift, so I submit incomplete prompt. I know who pay for pro have unlimited prompts, but I'm sure implementing this feature can help Copilot team to offer better ed efficient service with minor infrastructure cost.
Thanks

PS: apologize me for my bad english. I'm italian and I know my limit. I try to do my best.

[thevibingteen]

This is actually a very good UX suggestion 👍 You’re not alone — many users face the same “accidental send” issue.

Having a setting like:

Enter = Send message

Enter = New line (Send via button)

would improve usability, especially for long or structured prompts.

You should consider submitting this as a feature request/feedback directly through GitHub Copilot feedback channels so the product team can track it:

VS Code: Help → Report Issue → Copilot

Or GitHub Feedback Discussions (if available for Copilot)

Also don’t worry about your English — your idea is very clear and understandable 👌 Keep sharing feedback like this, it genuinely helps improve the product.

[krishkhinchi]

Hi @Genymus,

Great suggestion. A configurable Enter key behavior would improve usability and reduce accidental prompt submissions, especially for multiline prompts. Offering both modes (Enter to send vs Enter for newline) would be a simple but valuable UX improvement.

If this answer solves your doubts, please mark it as Answered. If not, feel free to share what’s still unclear.

[Genymus]

@krishkhinchi
I accepted the answer, but what should I do now to forward it to the copilot development team?

[krishkhinchi]

Thanks @Genymus for mark me as a answer

You don’t need to forward it manually. Since this discussion is already posted under Copilot Conversations → Product Feedback and marked as Answered, it is automatically visible to the Copilot product and engineering teams. They regularly review feedback from these discussions.

If you want to increase visibility (optional):

• Ask others to 👍 react or comment on the discussion
• Share the discussion link in similar Copilot feedback threads
• Submit the same link via GitHub Support → Copilot feedback if it’s critical for your workflow

[tangledhelix]

It would even be better if it were the default behavior that enter does not send the request. As I type this remark, for instance, enter will not send my comment. It is only in the chat context that Github chose to break from their previous input model.

Claude has this behavior by default. It is a much more usable experience than either Github Copilot or ChatGPT, IMHO. But if it cannot be the default behavior, I would love to see it at least configurable.

My suggestion would be to make it the default behavior for any new users who start using Copilot, so as not to disrupt existing people. But to offer the option to everyone so they may choose.

(Just making the point that my post, like all other posts in this discussion, has multiple line breaks, this would have been annoying to write with the behavior copilot uses.)