fix: only show configured providers in model list

[wtj-0527]

Problem

WebUI shows all hardcoded providers (OpenAI, Anthropic, Google, etc.)
even when they are not configured in config.yaml, giving users a false
impression that these providers are available.

Root Cause

get_available_models() in api/config.py auto-detects providers from
credential_pool and environment variables, then displays
models from _PROVIDER_MODELS for any detected provider, regardless
of whether the user actually configured them.

Solution

1. Disable auto-detection from credential_pool (removed)
2. Disable auto-detection from environment variables (removed)
3. Only show providers that are explicitly configured in config.yaml
   • model.provider setting (active_provider)
   • providers section in config.yaml
4. Keep live model fetching for custom provider with base_url configured
5. Update model group building to only use configured providers

Testing

• Before: /api/models shows OpenAI, Anthropic, Other groups with
  hardcoded models, even when not configured
• After: /api/models only shows providers configured in config.yaml
  or the active_provider
• Verified: Custom provider with base_url still works correctly
• Principle: "only show what the user explicitly configured"

Related

• Closes the gap identified in PR fix: restore profile API and clean up config #1264 (closed but partial fix needed)
• Follows the configuration-first principle: "configure once, use everywhere"

[nesquena-hermes]

Thanks for the well-structured PR, @KingBoyAndGirl!

What this does: Filters the /api/models response so only providers explicitly configured in config.yaml (via model.provider or the providers section) appear in the model picker — eliminating the confusing "ghost" provider groups that show when credentials happen to be present in the environment.

On the two-commit evolution: The first commit removed auto-detection entirely; the second backed off to add a only_show_configured_providers config flag (default: false) so existing behaviour is preserved unless the user opts in. That's the right call — it avoids a silent breaking change for users who rely on env-var detection today.

A few things for maintainer review:

• The flag name only_show_configured_providers is clear but slightly long. Consider providers.only_configured: true to keep it in a providers: namespace alongside future provider settings.
• It's worth confirming the /api/models unit tests (or at least the snapshot of returned groups) still pass with both false (default) and true so CI catches regressions.
• Related: issue Clarify and harden Provider/Model source-of-truth across WebUI, CLI, and Gateway #1240 tracks the broader provider source-of-truth work — this PR is a clean step in that direction.

Overall approach is sound. Leaving for maintainer sign-off on the flag naming and test coverage.

[wtj-0527]

Thanks for the suggestion! 🎉

I've updated the PR to follow the providers.only_configured naming as recommended:

• Moved config from top-level only_show_configured_providers to providers.only_configured
• This keeps provider-related settings properly namespaced
• Default behavior unchanged (false when not set)

The latest commit has been pushed. Would you like me to add/update tests for both false (default) and true cases? Happy to do so if it helps with the merge. 😊

[nesquena-hermes]

Thanks for the quick update, @KingBoyAndGirl!

The rename to providers.only_configured is the right call — it keeps provider-related config properly namespaced and matches the pattern used elsewhere in the config structure.

On your question about tests: yes, adding explicit test cases for providers.only_configured: false (default behavior — all providers shown) and providers.only_configured: true (filtered to configured providers only) would be helpful before merge. The existing behavior is that unconfigured providers should still appear when the flag is not set, so a test confirming that default is preserved is worth having.

Everything else looks good.

[wtj-0527]

Tests added! 🎉

I've added a new test class TestOnlyConfiguredProviders in tests/test_issue1106_custom_providers_models.py with 4 test cases:

✅ test_only_configured_false_shows_configured_providers - Verifies configured providers appear when false
✅ test_only_configured_true_filters_to_configured - Verifies only configured providers appear when true
✅ test_only_configured_true_with_active_provider - Active provider always appears when true
✅ test_only_configured_default_is_false - Backward compatibility check (default behavior)

All tests pass! 🚀

Latest commit: 1b71f13 - test: add test cases for providers.only_configured

Ready for review! 😊

[nesquena-hermes]

✅ Merged into release branch — included in PR #1285 (v0.50.240). Thanks for the contribution!

[nesquena-hermes]

Shipped in release v0.50.240 (PR #1285). Thanks!