You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've just stumbled across something that isn't documented that way and it actually solves a headache I was having. I am very delighted.
Providing LibreChat to users with no deep technical understanding requires the use of modelSpecs. The way we are doing it, is configuring modelSpecs for several LibreChat agents, thus providing these agents to all users via the simple selection in the upper left.
We do not want to provide model selections through our Azure endpoints, let alone the possibility to configure presets or parameters.
Therefore we're disabling modelSelect, presets and parameters via interface.
While modelSpecs work great for this purpose, we've always been missing the otherwise great menu of My agents, that disappears alongside with the direct model selection when setting modelSelect to false.
We would've loved to use modelSpecs AND have the My agents menu, which shows all agents to which a user has more than just Viewer access.
Because the downside of using modelSpecs + the agent marketplace, is that while agents used for chats from the marketplace work great, the LibreChat UI shows 'Select a model' in the upper left menu while such a marketplace agent is used. Not a functional, but a visual inconvenience.
Now for the discovery I've just made:
I have set these interface settings in librechat.yaml:
That alone would enable model selection in the menu, which we don't want to have, regardless of whether a modelSpecs list is also active.
Now on top I have configured this for our modelSpecs:
modelSpecs:
enforce: false
prioritize: true
addedEndpoints:
- agents
list:
- name: "ABC_Agent"
label: "ABC AI-Agent"
description: "Your AI for general purposes"
iconURL: https://www.librechat.ai/favicon.ico
preset:
default: false
endpoint: "agents"
agent_id: "agent_abcdefghijklmnop1"
The documentation does not list the agents as an allowed endpoint for addedEndpoints.
However, this works great and adds the My agents menu to the upper left menu, while leaving the direct model selections out.
Exactly what we needed. Because this little trick fixes the issue with 'Select a model' being displayed when an agent from the marketplace is used to start a chat.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I've just stumbled across something that isn't documented that way and it actually solves a headache I was having. I am very delighted.
Providing LibreChat to users with no deep technical understanding requires the use of
modelSpecs. The way we are doing it, is configuringmodelSpecsfor several LibreChatagents, thus providing these agents to all users via the simple selection in the upper left.We do not want to provide model selections through our Azure endpoints, let alone the possibility to configure
presetsorparameters.Therefore we're disabling
modelSelect,presetsandparametersviainterface.While
modelSpecswork great for this purpose, we've always been missing the otherwise great menu ofMy agents, that disappears alongside with the direct model selection when settingmodelSelecttofalse.We would've loved to use
modelSpecsAND have theMy agentsmenu, which shows all agents to which a user has more than justVieweraccess.Because the downside of using modelSpecs + the agent marketplace, is that while agents used for chats from the marketplace work great, the LibreChat UI shows 'Select a model' in the upper left menu while such a marketplace agent is used. Not a functional, but a visual inconvenience.
Now for the discovery I've just made:
I have set these
interfacesettings inlibrechat.yaml:That alone would enable model selection in the menu, which we don't want to have, regardless of whether a
modelSpecslist is also active.Now on top I have configured this for our
modelSpecs:The documentation does not list the
agentsas an allowed endpoint foraddedEndpoints.However, this works great and adds the My agents menu to the upper left menu, while leaving the direct model selections out.
Exactly what we needed. Because this little trick fixes the issue with 'Select a model' being displayed when an agent from the marketplace is used to start a chat.
Beta Was this translation helpful? Give feedback.
All reactions