LibreChat
-
@jdaviescoates Tired, impatient, and time-sensitive. Sorry!
If you get anything from me here it is always to save time, our most precious resources, and I have a lot less of it left them most.
Doubly impatient when I have to resize screenshots up upload them to this NodeBB setup, but here we are...
- https://www.librechat.ai/docs/features/agents
- https://www.librechat.ai/docs/features/agents#sharing-and-permissions
It's all there in the docs.
This is an "Agent" (what Poe.com calls a "App". You only have to use Poe.com for 30 seconds to get what they are.)
Create these, and have a server-hosted (Cloudron-hosted) instance of LibreChat, and now your pre-trained "Agents" (in LibreChat lingo), can be shared.
This feature just doesn't exist in OpenWebUI, and I can't see it coming any time soon.
The difference to me with having LibreChat on Cloudron is probably $100/month plus compared to doing the same with Poe.com. Plus not having my knowledge training setups locked up in someone else's SaaS.
Plus, frickin hours, and hours, and hours of long-hand wasted time teaching a team how to all setup the same pre-trained chat, and keep updating it as it is refined — when this is an already a solved problem but LibreChat Agents and sharing those Agents among users on the same server. Not conversations. Agents. AKA Apps in Poe.com language.
With the bridge between problem and solution apparently being persuasion that there is a LOT more value to this in LibreChat, and this specific highly valuable time, money and settings-saving thing value is not in OpenWebUI.
If you don't work with a team, you probably don't need it.
If you work with a team, and are going to be using AI, then this has a lot of value that I'm not seeing anywhere else.
That's the use-case and value-proposition.
Is there anyone left in this thread that still doesn't get it?
@marcusquinn said in LibreChat:
Doubly impatient when I have to resize screenshots up upload them to this NodeBB setup, but here we are...
ShareX with (on Cloudron) Xbackbone are brilliant for screenshotting. If you regularly use screenshots, it is invaluable.
-
I am pretty happy with this in openwebui:
But I will take a look at librechat, just had no desire to look for something else so far.@NCKNE Thanks. Not seen that before. I'm not a fan of the WebUI interface, but it it's possible, it is highly valuable! Thanks for the pointer, I'll give it a try.
-
@marcusquinn said in LibreChat:
Doubly impatient when I have to resize screenshots up upload them to this NodeBB setup, but here we are...
ShareX with (on Cloudron) Xbackbone are brilliant for screenshotting. If you regularly use screenshots, it is invaluable.
@LoudLemur Thanks. I'm using Shottr, and just found the resize x0.5 option, so that seems to work.
-
@NCKNE Thanks. Not seen that before. I'm not a fan of the WebUI interface, but it it's possible, it is highly valuable! Thanks for the pointer, I'll give it a try.
@marcusquinn You‘re welcome. We are using openwebui with RAG (our own documents aka knowledge) for the IT support team. We are using it on cloudron together with the private IONOS AI Hub. Great service if you are serving EU customers.
-
@marcusquinn You‘re welcome. We are using openwebui with RAG (our own documents aka knowledge) for the IT support team. We are using it on cloudron together with the private IONOS AI Hub. Great service if you are serving EU customers.
@NCKNE V Interesting. Great share. Thanks you!
-
Open WebUI has changed their license to a not-strictly-open-source license (by OSI definition):
https://docs.openwebui.com/license/
https://www.reddit.com/r/LocalLLaMA/comments/1kg4avg/openwebui_license_change_red_flag/
-
@canadaduane thanks for the heads up . https://docs.openwebui.com/license/#open-webui-license-explained has an ELI5 of sorts
-
M marcusquinn referenced this topic on
-
C charlesnw referenced this topic on
-
There’s actually a deeper issue concerning Open WebUI, beyond just the recent switch to a non-OSI license. The sole maintainer’s demand for contributor license agreements (CLAs), along with how he's communicated and managed these changes, creates genuine uncertainty.
Given this scenario, the risk of further license changes becoming problematic for Cloudron users isn't far-fetched. To mitigate this, proactively packaging LibreChat would be strategically smart. It ensures Cloudron users always have immediate access to reliable, fully open-source software, especially if Open WebUI's licensing situation deteriorates further.
-
We now have a working LibreChat cloudron container set up. See: https://forum.cloudron.io/topic/12850/first-try-app-packaging-librechat-issue-with-postgresql-extention-pgvector/14?_=1749416165430
