Not the op but I use chatblade[0] on the cli, chatgpt-next-web[1] as webgui and quivr[2] for multimodal stuff files/images/audio/video. atm everything goes over a azure openai endpoint but would love to infere an llm locally.

[0] https://github.com/npiv/chatblade

[1] https://github.com/Yidadaa/ChatGPT-Next-Web/

[2] https://github.com/StanGirard/quivr

Is there much difference between the Azure endpoint and the direct OpenAI endpoint?

I really wonder this too.

At work we're always told to use the Azure one because our CIO is elbow deep in Microsoft's ass.

But I wonder.. one funny thing is that everyone at Microsoft is referring to OpenAI as an 'acquisition' whereas as far as I know they only have a <50% interest?

It's mostly speed and that you can disable the constraints openai uses on their API and chatgpt. You have to write a motivational letter though...

If it's useful, I recently open-sourced a simple GPT-4 TUI [1], which I use many times a day. And since this is a Kagi post, I might as well plug my (extremely simple) Kagi CLI [2], which uses their FastGPT API under the hood.

[1] https://git.sr.ht/~bsprague/gpt4-tui

[2] https://github.com/bcspragu/kagi

Simon Willison’s `llm` is an excellent command line client, and now has `llm chat` as well as `-c` for ongoing conversations.

https://llm.datasette.io/en/stable/

I use the ChatGPT bot for matrix mainly. I've tried some other frontends that are more like ChatGPT web but I keep going back to matrix because it's just so handy. I have all my other chats in there too, through bridges.

I use the OpenAI playground because I'm paranoid that third party frontends will steal my API keys and I don't have enough time to audit the code or set up firewall rules.

You can set up a spending limit on the API anyway. It's pretty low risk IMO.

chatgpt-cli is a great tui