Originally created by @AlexZorzi on GitHub (Oct 28, 2025).
Check Existing Issues
I have searched all existing open AND closed issues and discussions for similar requests. I have found none that is comparable to my request.
Problem Description
Im managing an org, i only want them to use 1 single AI model that is good enough for general tasks. My users are not tech savvy. From a price angle using a tiny cheap model to generate chat titles saves me a lot of money.
I have a few workspace models with a custom system script and the users end up switching between them, sometimes they end up clicking the public model that its used to make titles and they will complain about the poor quality output.
Desired Solution you'd like
Move the Title generation server side if its not already, and allow the admins to pick a private Model to generate the titles so that it wont appear as a chat option on the users interface.
Alternatives Considered
keep the model "public" but add a button to hide a specific model from the model selector
Additional Context
setting is in /admin/settings/interface
Originally created by @AlexZorzi on GitHub (Oct 28, 2025).
### Check Existing Issues
- [x] I have searched all existing open AND closed issues and discussions for similar requests. I have found none that is comparable to my request.
### Problem Description
Im managing an org, i only want them to use 1 single AI model that is good enough for general tasks. My users are not tech savvy. From a price angle using a tiny cheap model to generate chat titles saves me a lot of money.
I have a few workspace models with a custom system script and the users end up switching between them, sometimes they end up clicking the public model that its used to make titles and they will complain about the poor quality output.
### Desired Solution you'd like
Move the Title generation server side if its not already, and allow the admins to pick a private Model to generate the titles so that it wont appear as a chat option on the users interface.
### Alternatives Considered
keep the model "public" but add a button to hide a specific model from the model selector
### Additional Context
<img width="1046" height="174" alt="Image" src="https://github.com/user-attachments/assets/db237e9d-191a-4142-96e7-de35937bc2f1" />
setting is in /admin/settings/interface
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @AlexZorzi on GitHub (Oct 28, 2025).
Check Existing Issues
Problem Description
Im managing an org, i only want them to use 1 single AI model that is good enough for general tasks. My users are not tech savvy. From a price angle using a tiny cheap model to generate chat titles saves me a lot of money.
I have a few workspace models with a custom system script and the users end up switching between them, sometimes they end up clicking the public model that its used to make titles and they will complain about the poor quality output.
Desired Solution you'd like
Move the Title generation server side if its not already, and allow the admins to pick a private Model to generate the titles so that it wont appear as a chat option on the users interface.
Alternatives Considered
keep the model "public" but add a button to hide a specific model from the model selector
Additional Context
setting is in /admin/settings/interface
@tjbck commented on GitHub (Oct 28, 2025):
You should hide models instead.