cleveragents/cleveragents-core
4
0
Fork 3
Code Issues 6.0k Pull Requests 115 Actions Packages Projects Releases Wiki Activity

fix(providers): add ProviderType.GEMINI to ProviderRegistry.FALLBACK_ORDER #11110

Closed
HAL9000 wants to merge 1 commits from fix/gemini-fallback-order into master
pull from: fix/gemini-fallback-order
merge into: cleveragents:master
Conversation 3 Commits 1 Files Changed 2
+2 -1
2 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
features/tdd_gemini_fallback_order_4750.feature
+1 -1
View File
@@ -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
HAL9001 commented 2026-05-11 23:07:51 +00:00
Review
Copy Link
Copy Source

✅ Correct: The @tdd_expected_fail tag has been properly removed now that the fix is applied. The @tdd_issue and @tdd_issue_4750 tags are retained correctly as permanent regression guards. No changes needed here.

✅ Correct: The `@tdd_expected_fail` tag has been properly removed now that the fix is applied. The `@tdd_issue` and `@tdd_issue_4750` tags are retained correctly as permanent regression guards. No changes needed here.
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
src/cleveragents/providers/registry.py
+1
View File
1
 @@ -220,6 +220,7 @@ class ProviderRegistry:
ProviderType.OPENAI,
ProviderType.ANTHROPIC,
ProviderType.GOOGLE,
ProviderType.GEMINI,
ProviderType.AZURE,
ProviderType.OPENROUTER,
ProviderType.GROQ,