Make sure you've configure llm first (https://llm.datasette.io/en/stable/)
I'd love to get feedback, PRs and who knows, perhaps a coffee! https://buymeacoffee.com/icarito
Show HN: Light like the Terminal – Meet GTK LLM Chat Front End
github.com
1–10 of 15 posts
Make sure you've configure llm first (https://llm.datasette.io/en/stable/)
I'd love to get feedback, PRs and who knows, perhaps a coffee! https://buymeacoffee.com/icarito
Show HN: Light like the Terminal – Meet GTK LLM Chat Front End
github.com
This looks quite nice. I would like to see the system prompt and inference parameters exposed in the UI, because those are things I'm used to fiddling with in other UIs. Is that something that the llm library supports?
It’d be better if it was written in C or at least Vala. With Python, you have to wait a couple hundred milliseconds for the interpreter to start, which makes it feel less native than it can be. That said, the latency of the LLM responses is higher than the UI, so I guess the slowness of Python doesn’t matter.
I've been pondering whether to backport to GTK3 for this sole purpose. I find that after the initial delay to startup the app, its speed is okay...
Porting to Rust is not really planned because I'd loose the llm-python base - but still something that triggers my curiosity.
This looks quite nice. I would like to see the system prompt and inference parameters exposed in the UI, because those are things I'm used to fiddling with in other UIs. Is that something that the llm library supports?
Yeah absolutely, I've just got to point where I'm happy with the architecture so I'll continue to add UI. I've just added support for fragments and I've thought to add them as if they were attached documents. I've in the radar to switch models in mid conversation and perhaps the ability to rollback a conversation or remove some messages. But yeah, system prompt and parameters would be nice to move too! Thanks for the…
It’d be better if it was written in C or at least Vala. With Python, you have to wait a couple hundred milliseconds for the interpreter to start, which makes it feel less native than it can be. That said, the latency of the LLM responses is higher than the UI, so I guess the slowness of Python doesn’t matter.
It’d be better if it was written in C or at least Vala. With Python, you have to wait a couple hundred milliseconds for the interpreter to start, which makes it feel less native than it can be. That said, the latency of the LLM responses is higher than the UI, so I guess the slowness of Python doesn’t matter.
What's the startup time now with 9950X3D, after a prior start so the pyc's are cached in RAM?
Does this work on Mac or Linux only?