Why Ctrl+D ?

[devlux76]

I had a laughable experience last night where the AI sort of went off the rails and I had to pskill it because I couldn't get it to stop.

Today I decided to review the code to figure out how one is supposed to stop the chat function.
Turns out it's Ctrl+D

For all of history the kill this process shortcut has been Ctrl+C although Ctrl+Z could put it to sleep / background it.

I'm not questioning your design, it's an awesome project, I love it and I can't wait to jump in with both feet. However, why deviate from long established UX standards?

[ErikBjare]

It was Ctrl+C for a long time, but it often resulted in accidentally killing the entire process when trying to cancel something and going ham on Ctrl+C (leading to a lot of gptme -r)

So I changed it to work like other shells, where to exit you need a Ctrl+D (EOF) at the prompt (or /exit). You should still be able to interrupt the assistant and any tool uses with Ctrl+C, which should bring you right back to the User: prompt (there may be bugs where such is not the case, which I'd appreciate reproducible reports for).

I've learned the new behavior and like it, but you are the second person to ask in a few days, so maybe confusing and something to address.

[devlux76]

Maybe just add a note... "It looks like you're trying to exit, ctrl+c interrupts the bot, use ctrl+d or /exit to exit the chat"

Also /bye is used by ollama, so perhaps that one as well.
I tried /exit but it didn't work and I don't know why. It may be because my AI was having a seizure talking about why the sky is made of cheese at the time.