Add setting to customize how the Enter key behaves in prompt input field

[Alek2077]

Add an option in the settings (or in a visible, easily accessible place) to switch between:

Enter = newline / Shift+Enter or Ctrl+Enter = send

Enter = send / Shift+Enter = newline (current default)

This flexibility improves ergonomics for users who write long or structured prompts and want faster multiline input without holding modifier keys. Those of us typing hundreds of words per prompt find it physically tiring to hold Shift constantly, and we occasionally send prompts by mistake when we forget.
Google AI Studio does this by default.

Why it matters:

• Reduces finger fatigue from constantly holding Shift
• Prevents accidental prompt submissions due to missed Shift
• Aligns with common editors and markdown interfaces
• Improves usability for power users writing structured input manually

[nikhil-swamix]

also add current file in context like how continue.dev does would be good?
alt+enter = add current file and send (instructs to only work with current open file, and no searching relevant files across codebase!)

[brunobergher]

We need to be thoughtful about every setting we add, since it's hard to remove and adds carrying cost, but this is indeed a very central piece of the UX, so I think it can be reasonable to add the ability to switch between these two in settings. We'll probably need a new settings tab for "UI" or something like that, where this and some other stuff will eventually go.

On the shortcut for current file @ + the first letter of the current file already seems to me like a very quick way of doing it, so I don't think we need a dedicated shortcut. I'll Alt+Enter in mind for the future as a possible "special" shortcut users could pick what to do with (eg pull current file, pull terminal content, etc) according to their usage pattern. But I'd keep these separate.

[Alek2077]

@brunobergher We should be mindful about adding 'anything' to any app unless needed, but this can directly affect the waste of API tokens, and is a plus for usability. It's one of those things that can be implemented and to have it 'sit' in the settings. You don't have to change the app too much or change the default functionality; you don't even need to tell the user this setting exists. Yet, it can benefit a lot of us.

As for how to do it, I'll withold suggesting any particulars. I can say as an end user, all I need is a way to quickly make a few newlines and go to the next row. Typically an Enter/Return key is used for this, so I think that makes sense. As noted above, a simple Shift/Ctrl/Alt+Enter could be used for sending the request, though it doesn't matter what this combination is - it can be any combination as long as it's not just a simple key that can be mistakenly pressed. The Settings can offer this flexibility to choose what is available. Please keep in mind that recently for Windows users a key combination 'Ctrl+Y' was added to Roo and it was detrimental for WSL users as this command is for redo. If adding this, please don't choose something as crucial, or offer the ability to change Roo shortcuts.

[brunobergher]

The token waste argument makes this even more valuable, for sure.

Also, for context, I'm the person responsible for design (and other things) at Roo now, hence my more prescriptive solution. The idea is to make it easier for anyone who wants to submit a PR to produce something we're likely to accept.

On KB shortcuts, I totally agree. We've been moving to use customizable (in VSCode) shortcuts in general, and been hunting a lot more for conflicts when adding anything.

Are you interested in taking this on? I'm sure Roo can get a good chunk of it done :)

[KanTakahiro]

I am totally agree with @Alek2077 . I use 3 languages (English/Chinese/Japanese) when I chat with Roo. This topic actually affects me more than other English speakers. Because in usual CJK input method, Enter key plays a role.
For example, in Chinese input method, after you type some alphabets, you can hit Space key to get Chinese characters, and you can also hit Enter key to get the alphabets you typed. When you write a Chinese sentence but there are some English words in the sentence (example: 我需要該Class具有以下功能), you should type some alphabets → hit Space → type some alphabets → hit Enter → type some alphabets → hit Space.
And in Japanese input method, you hit Enter to get the Japanese characters, in macOS build in Japanese input method, you have to hit two times. So when using a Japanese input method, it's easy to accidentally press Enter key too many times.
I've lost count of how many times I've accidentally pressed or multi-pressed the Enter key while using Roo, causing my unfinished prompt to be sent. This not only disrupts my workflow but also incurs extra token costs.
Currently, I write the prompt in another code editor and then copy and paste it into Roo. This hassle could be solved with a simple “Press Ctrl+Enter to send” feature.

[brunobergher]

Feel free to submit a PR! We now have a "UI" section in settings where this can easily go.

[lmtr0]

I've implemented it here #8556

I would appreciate it if anyone could help out with documentation and tests; I don't have time to implement it.

cc @brunobergher @KanTakahiro @Alek2077