Skip to content

fix(model-switch): separate picker rows for same-endpoint proxies with distinct names (salvages #67747) - #67925

Merged
teknium1 merged 1 commit into
mainfrom
salvage/proxy-name-grouping
Jul 20, 2026
Merged

fix(model-switch): separate picker rows for same-endpoint proxies with distinct names (salvages #67747)#67925
teknium1 merged 1 commit into
mainfrom
salvage/proxy-name-grouping

Conversation

@teknium1

Copy link
Copy Markdown
Contributor

Summary

custom_providers: entries sharing one endpoint but carrying distinct display names (aggregating proxies — LiteLLM fronting cerebras/groq/perplexity at a single URL) now get separate picker rows instead of silently merging into one. Salvages #67747 (@craigdfrench) onto current main with authorship preserved.

Changes

Credit also to @chiyema#21544 proposed the name-discriminator concept first (May 7); its implementation predated the credential/mode/headers hardening and would have regressed it.

Validation

Check Result
test_model_switch_custom_providers.py + test_provider_section3_grouping.py + test_list_picker_providers.py 68/68 pass
E2E, real imports: mixed config with section-3 providers: (Palantir 2-entry fold) + section-4 proxy entries section 3 still folds by endpoint identity ("Palantir Claude", 2 models); section 4 yields separate Cerebras/Groq rows — no interference with #67908

Infographic

proxy-provider-grouping

@alt-glitch alt-glitch added type/bug Something isn't working comp/cli CLI entry point, hermes_cli/, setup wizard area/config Config system, migrations, profiles P3 Low — cosmetic, nice to have needs-decision Awaiting maintainer decision before any implementation sweeper:risk-compatibility Sweeper risk: may break existing users, config, migrations, defaults, or upgrades labels Jul 20, 2026
@alt-glitch

Copy link
Copy Markdown
Collaborator

This was generated by AI during triage.

Maintainer salvage of #67747 and related to #21544. It carries the same display-prefix idea but preserves the newer credential/mode/header grouping contract, so maintainers should choose the current-main-aware implementation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/config Config system, migrations, profiles comp/cli CLI entry point, hermes_cli/, setup wizard needs-decision Awaiting maintainer decision before any implementation P3 Low — cosmetic, nice to have sweeper:risk-compatibility Sweeper risk: may break existing users, config, migrations, defaults, or upgrades type/bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants