Skip to content

Conversation

@insertmike
Copy link

Abstract

Add optional model_group field to ModelRecord interface and populate it for all models in prebuiltAppConfig. This enables consumers to filter and organize models by their family (e.g., "Llama", "Qwen", "Phi", "Gemma").

Model families are consistently grouped:

  • All Llama versions grouped as "Llama"
  • All Qwen versions grouped as "Qwen" (includes Coder/Math variants)
  • All Phi variants grouped as "Phi"
  • All Gemma variants grouped as "Gemma"
  • All Hermes variants grouped as "Hermes"
  • All DeepSeek variants grouped as "DeepSeek"
  • All TinyLlama versions grouped as "TinyLlama"
  • Other families: Mistral, SmolLM2, StableLM, RedPajama, Snowflake

This change is backward compatible as the field is optional.

…tion

Add optional `model_group` field to ModelRecord interface and populate it for
all models in prebuiltAppConfig. This enables consumers to filter and
organize models by their family (e.g., "Llama", "Qwen", "Phi", "Gemma").

Model families are consistently grouped:
- All Llama versions grouped as "Llama"
- All Qwen versions grouped as "Qwen" (includes Coder/Math variants)
- All Phi variants grouped as "Phi"
- All Gemma variants grouped as "Gemma"
- All Hermes variants grouped as "Hermes"
- All DeepSeek variants grouped as "DeepSeek"
- All TinyLlama versions grouped as "TinyLlama"
- Other families: Mistral, SmolLM2, StableLM, RedPajama, Snowflake

This change is backward compatible as the field is optional.
@insertmike insertmike changed the title feat(config): add model_group field to ModelRecord for model organiza… feat(config): add model_group field to ModelRecord for model org Nov 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant