Repository navigation
Allow hiding custom endpoints from user-facing model selection #17061
Replies: 1 comment
|
Hey @izabel-usheva did you already have a look at the modelSpecs config here? I think that could solve your problem described here and also your problem with the user-friendly names, which you try to solve.
Let's assume you have some kind of config like this right now: I would suggest that you add the following This will now give you two groups in your model-select dropdown in the Chat-UI:
Furthermore, If you're not using the agents feature, just omit the line But if you do also use the agents feature, I would suggest adding this in the endpoints config: Just list all endpoints in Hope that helps. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Problem
I use a dedicated custom endpoint for conversation title generation through
titleEndpointandtitleModel. This endpoint should remain available for title generation, but it should not be offered as a chat endpoint.Currently, it appears in the model selector even though users are not intended to use it for conversations.
Proposed solution
Add an optional
visibleproperty to custom endpoints inlibrechat.yaml:When visible: false:
Omitting visible should preserve the existing behavior. This setting controls UI visibility and automatic selection, not access permissions.
Implementation approach
Apply the visibility rule in the shared endpoint mapping and default-selection logic so that all relevant UI entry points behave consistently.
I created a PR - #17058
All reactions