Feature Description
A recipe named user.gemma4.mysuperduperquant is already dot-delimited. If multiple recipes share a segment at the same level — e.g. user.gemma4.quantA and user.gemma4.quantB — they'd be visually grouped under a gemma4 header in the UI, with each variant showing its own load/delete/settings controls.
The grouping should be purely dynamic, derived from the existing naming convention rather than requiring a fixed "org" or "model" taxonomy.
If two names happen to share a segment at the same tree level, they group. No semantic meaning is imposed on any particular level.
Scope (intentionally minimal):
This is a quality-of-life improvement, not a deep restructuring.
Specifically as noted @jeremyfowers:
user. prefixed models should probably remain expanded by default, since users expect to find them immediately after downloading.
Example:
Would become:
Use Case / Motivation
When users accumulate multiple model recipes, the flat list becomes hard to navigate. This proposes automatically grouping recipes that share a common string at the same level in their dot-separated name hierarchy.
Platform Relevance
All platforms
Additional Context
All UI's
Feature Description
A recipe named user.gemma4.mysuperduperquant is already dot-delimited. If multiple recipes share a segment at the same level — e.g. user.gemma4.quantA and user.gemma4.quantB — they'd be visually grouped under a gemma4 header in the UI, with each variant showing its own load/delete/settings controls.
The grouping should be purely dynamic, derived from the existing naming convention rather than requiring a fixed "org" or "model" taxonomy.
If two names happen to share a segment at the same tree level, they group. No semantic meaning is imposed on any particular level.
Scope (intentionally minimal):
This is a quality-of-life improvement, not a deep restructuring.
Specifically as noted @jeremyfowers:
user. prefixed models should probably remain expanded by default, since users expect to find them immediately after downloading.
Example:
Would become:
Use Case / Motivation
When users accumulate multiple model recipes, the flat list becomes hard to navigate. This proposes automatically grouping recipes that share a common string at the same level in their dot-separated name hierarchy.
Platform Relevance
All platforms
Additional Context
All UI's