Skip to content

fix: use named custom provider credentials#18804

Open
yingjialong wants to merge 1 commit into
NousResearch:mainfrom
yingjialong:fix/custom-provider-same-url-keys
Open

fix: use named custom provider credentials#18804
yingjialong wants to merge 1 commit into
NousResearch:mainfrom
yingjialong:fix/custom-provider-same-url-keys

Conversation

@yingjialong

Copy link
Copy Markdown

Summary

  • keep custom provider picker rows tied to each provider's stable slug, even when multiple providers share the same gateway base URL
  • resolve named custom providers with their configured api_key / key_env before falling back to a shared custom credential pool
  • add regression coverage for same-base-url/different-key custom providers and the remaining pool fallback path

Test plan

  • python -m py_compile hermes_cli/model_switch.py hermes_cli/runtime_provider.py tests/hermes_cli/test_model_switch_custom_providers.py tests/hermes_cli/test_runtime_provider_resolution.py
  • python -m pytest tests/hermes_cli/test_model_switch_custom_providers.py tests/hermes_cli/test_runtime_provider_resolution.py -q

Keep /model picker rows tied to each custom provider's stable slug, even when multiple providers share a gateway base URL. Resolve named custom providers with their configured API key or key_env before falling back to the shared custom credential pool, so model validation sees the selected provider's /models listing.
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 P2 Medium — degraded but workaround exists type/bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants