From e9cf6d9658e10ca09e7b0753fdbca2eee419a59a Mon Sep 17 00:00:00 2001 From: CleverThis Date: Mon, 11 May 2026 00:56:34 +0000 Subject: [PATCH] fix(providers): add ProviderType.GEMINI to ProviderRegistry.FALLBACK_ORDER Adds ProviderType.GEMINI to the provider registry fallback order, right after ProviderType.GOOGLE. This ensures Gemini-only users can use auto-discovery via get_default_provider_type() when only GEMINI_API_KEY is set. Also removes the @tdd_expected_fail tag from the TDD scenario in features/ tdd_gemini_fallback_order_4750.feature since the test now passes. --- features/tdd_gemini_fallback_order_4750.feature | 2 +- src/cleveragents/providers/registry.py | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/features/tdd_gemini_fallback_order_4750.feature b/features/tdd_gemini_fallback_order_4750.feature index 882e2f08e..04d614b10 100644 --- a/features/tdd_gemini_fallback_order_4750.feature +++ b/features/tdd_gemini_fallback_order_4750.feature @@ -3,7 +3,7 @@ Feature: TDD: ProviderType.GEMINI missing from ProviderRegistry.FALLBACK_ORDER I want get_default_provider_type() to return ProviderType.GEMINI via the fallback chain So that Gemini-only users can use auto-discovery without setting GOOGLE_API_KEY - @tdd_issue @tdd_issue_4750 @tdd_expected_fail + @tdd_issue @tdd_issue_4750 Scenario: Gemini-only user gets GEMINI as default provider via fallback order Given a ProviderRegistry configured with only gemini_api_key set And CLEVERAGENTS_DEFAULT_PROVIDER is not set for tdd test diff --git a/src/cleveragents/providers/registry.py b/src/cleveragents/providers/registry.py index 5aafdfe85..81a36b83c 100644 --- a/src/cleveragents/providers/registry.py +++ b/src/cleveragents/providers/registry.py @@ -220,6 +220,7 @@ class ProviderRegistry: ProviderType.OPENAI, ProviderType.ANTHROPIC, ProviderType.GOOGLE, + ProviderType.GEMINI, ProviderType.AZURE, ProviderType.OPENROUTER, ProviderType.GROQ, -- 2.52.0