Enchancement - Add Group Folder/Button to models in bot

[ratu-sh]

Problem - When you use in bot many different providers with many different models - it is very hard to find needed one without sorting and filtering from one shared big list of models.

Enchancement - i think it could be good idea to add ability to group models in bot by your choice with environment variables.
So when you click on "/info - change model" - you will see not one shared list of all models - but several buttons with group names. and when you click button - than you see list of models only from that group.

for example you may group models by provider name (openrouter, grok, google, others), or by models family (gemini, llama, chatgpt, others) or by any another way.

for it purpose you can add some variables in environment like:

Environment="GET_MODELS=False"
#Environment="CUSTOM_MODELS=-all,***,***"
Environment="GROUP_MODELS=True"
Environment="GROUP_NAMES="gemini,llama,chatgpt,others"
Environment="GROUP_1=model-1-example,model-2-example"
Environment="GROUP_x=***"
Environment="GROUP_4=model-3-example,model-4-example"

[yym68686]

Hello, I don't think adding too many environment variables is a good idea. I cannot accept adding so many environment variables just to meet this one requirement. I hope there is a better way.

[ratu-sh]

Hello, I don't think adding too many environment variables is a good idea. I cannot accept adding so many environment variables just to meet this one requirement. I hope there is a better way.

than we can add in Environment only 1 variable with groups.yaml (or json or txt) path like that

Environment="GROUP_MODELS_PATH=\path\to\groups.yaml"

and groups.yaml will have this structure:

  - group: group-1
    button_name: openai
    models:
      - gpt-3.5-turbo
      - gtp-4o-mini
      - ***

  - group: group-2
    button_name: meta
    models:
      - llama-3.1-7b
      - llama-3.2-80b
      - ***
      
- group: group-3
    button_name: gemini
    models:
      - gemini-1.5-flash
      - gemini-1.5-pro
      - ***

[ratu-sh]

also, I think it might be a good idea to also move such variables from Environments to separate configuration files :

• CUSTOM_MODELS
• SYSTEMPROMPT
• whitelist
• BLACK_LIST
• ADMIN_LIST
• GROUP_LIST
  (all variables that may contains long text)
  and leave in Environments only the paths to them

maybe you could even move all variables from Environments to separate configuration files, but i don't know if it also good idea

[yym68686]

I need to carefully consider this feature and think of a more elegant way. Your customization requirements are too high and don't quite align with the out-of-the-box concept of this project. I need to find a balance. Once it's done, I will notify you here.I need to carefully consider this feature and think of a more elegant way. Your customization requirements are too high and don't quite align with the out-of-the-box concept of this project. I need to find a balance. Once it's done, I will notify you here.

[ratu-sh]

by default this variable and this config.yaml can be ommited and ignored - so it doesn't ruine out-of-the-box concept.
but only if somebody wish to implement groups/buttons logic - than it is supported by adding 1 variable and 1 config.yaml.