Assistant: Option to use Shift+Enter to send prompt instead of just Enter

Value7609

I just realized why I often send my prompts too early. It's because I press my Enter key thinking I'll create a new line. Instead, it sends the prompt directly. Currently, I use Shift+Enter to enter a new line. Is it possible to flip these, allowing me to use Enter normally, so I don't send my prompts too early. Perhaps there could be a toggle in the settings UI. I understand this might require JS, but I'm fine with that since I already allow JS on Kagi.

Vlad

Value7609 shift enter is the standard way to add a new line. the missing feature on our end is that after shift enter is used once, standard is for following 'enter's to also add a line where we currently treat it as send.

becausebirds

To second this, I use Kagi's fastGPT and want to Shift+Enter to create a new line and it just submits the query. Also, if the text entry box was freeform (multi-line) instead of a single line, it would greatly improve the experience.

PhilippeChoquette

Is it possible to change this behaviour on the mobile site? Because with the main Android keyboards, you can't mimic the Shift + Enter behaviour. In other words, it'll send as soon as you touch the Enter key.

I was trying Assistant for the first time earlier and it took me a minute to realize why it kept sending my queries before I had done writing them. It was slightly frustrating 😶

For reference, on the ChatGPT mobile app, which I use almost daily, pressing Enter adds new lines; it doesn't submit the query directly.

snicks0e

I’m having the same issue on mobile as well, hitting return on assistant searches immediately instead of entering a new line. This makes assistant nearly unusable for anything other than a simple search .

The standard in most other apps is to enter a new line instead of submitting on mobile. Messages, slack, even submitting this comment. I did notice on some forms, like google search, the return button on the keyboard changes to a blue “go” button (iOS) to signify it would submit instead of enter a new line

PhilippeChoquette

snicks0e they've finally corrected the behaviour! Thank you Kagi team!

https://kagi.com/changelog#4813

Multiline assistant queries on mobile #4693 @fxgn

(The actual issue of this post is still unchanged and in planned status)

Value7609

@Luis can be marked as done

Luis

Value7609 Ok, but we didn't make this change,

after shift enter is used once, standard is for following 'enter's to also add a line where we currently treat it as send.

Are you suggesting we consider closing the discussion without implementing this change?

IMO our setup is effective and intuitive as is:

shift+enter to create a new line
enter to prompt

Value7609

Luis yeah sorry I should have clarified it, I'm not really interested into flipping these keys anymore and also think that the current implementation is good as is.

I'm using it more often on mobile and there it works as intended.

PhilippeChoquette

Maybe OP created his post in the context of mobile use, so it is fixed for him. However, it could very well be relevant to implement what Vlad clarified this post to be about. I'm personally fine with the current behaviour too.

Luis

Ok, I'm closing this thread now. If anyone wishes to suggest changes to the discussed behaviour, please initiate a new thread. Thank you.

Thibaultmol

Maybe (def in the context of the feature being added) it make sense to change the title of this idea or atleast in the changelog to something like:

Assistant no longer submits when pressing enter on mobile, (enter creates newline instead)

or something like that.

Because i saw the title of this idea copy/pasted onto the changest but I don't know if that's really accurate