cleveragents/cleveragents-core

Fork 3

UAT: `ProviderType.GEMINI` missing from `FALLBACK_ORDER` — GEMINI-only users never get a provider selected #5810

New issue

Open

opened 2026-04-09 10:06:02 +00:00 by HAL9000 · 1 comment

HAL9000 commented

2026-04-09 10:06:02 +00:00

Owner

Bug Report

Feature Area: LLM Provider Backends
Milestone: v3.6.0
Severity: Priority/Backlog (GEMINI users affected when using fallback selection)

What Was Tested

Code-level analysis of src/cleveragents/providers/registry.py FALLBACK_ORDER and PROVIDER_KEY_ATTRS class variables.

Expected Behavior

ProviderType.GEMINI is a fully registered provider type with:

PROVIDER_KEY_ATTRS[GEMINI] = "gemini_api_key" ✓
DEFAULT_CAPABILITIES[GEMINI] defined ✓
DEFAULT_MODELS[GEMINI] = "gemini-2.0-flash" ✓

It should be included in the fallback order so that users who configure only GEMINI_API_KEY can have it automatically selected.

Actual Behavior

FALLBACK_ORDER in src/cleveragents/providers/registry.py (lines 204-213):

FALLBACK_ORDER: ClassVar[list[ProviderType]] = [
    ProviderType.OPENAI,
    ProviderType.ANTHROPIC,
    ProviderType.GOOGLE,      # ← GOOGLE is included
    ProviderType.AZURE,
    ProviderType.OPENROUTER,
    ProviderType.GROQ,
    ProviderType.TOGETHER,
    ProviderType.COHERE,
    # ProviderType.GEMINI is MISSING
]

ProviderType.GEMINI is absent from FALLBACK_ORDER. This means:

ProviderRegistry.get_default_provider_type() will never return GEMINI via fallback
FallbackSelector.select() will never select GEMINI
Users who set only GEMINI_API_KEY (without GOOGLE_API_KEY) will get "No AI provider configured" errors

Note: GOOGLE and GEMINI are separate provider types — GOOGLE uses GOOGLE_API_KEY while GEMINI uses GEMINI_API_KEY. A user who sets only GEMINI_API_KEY will not be served by the GOOGLE entry in FALLBACK_ORDER.

Code Location

FALLBACK_ORDER: src/cleveragents/providers/registry.py lines 204-213
PROVIDER_KEY_ATTRS: src/cleveragents/providers/registry.py lines 191-201

Impact

Users who configure GEMINI_API_KEY (the standard Google Gemini API key) instead of GOOGLE_API_KEY will not have their provider auto-selected. The FallbackSelector will also never select GEMINI as a fallback provider.

Automated by CleverAgents Bot
Supervisor: UAT Testing | Agent: uat-tester

## Bug Report **Feature Area**: LLM Provider Backends **Milestone**: v3.6.0 **Severity**: Priority/Backlog (GEMINI users affected when using fallback selection) ## What Was Tested Code-level analysis of `src/cleveragents/providers/registry.py` `FALLBACK_ORDER` and `PROVIDER_KEY_ATTRS` class variables. ## Expected Behavior `ProviderType.GEMINI` is a fully registered provider type with: - `PROVIDER_KEY_ATTRS[GEMINI] = "gemini_api_key"` ✓ - `DEFAULT_CAPABILITIES[GEMINI]` defined ✓ - `DEFAULT_MODELS[GEMINI] = "gemini-2.0-flash"` ✓ It should be included in the fallback order so that users who configure only `GEMINI_API_KEY` can have it automatically selected. ## Actual Behavior `FALLBACK_ORDER` in `src/cleveragents/providers/registry.py` (lines 204-213): ```python FALLBACK_ORDER: ClassVar[list[ProviderType]] = [ ProviderType.OPENAI, ProviderType.ANTHROPIC, ProviderType.GOOGLE, # ← GOOGLE is included ProviderType.AZURE, ProviderType.OPENROUTER, ProviderType.GROQ, ProviderType.TOGETHER, ProviderType.COHERE, # ProviderType.GEMINI is MISSING ] ``` `ProviderType.GEMINI` is absent from `FALLBACK_ORDER`. This means: 1. `ProviderRegistry.get_default_provider_type()` will never return `GEMINI` via fallback 2. `FallbackSelector.select()` will never select `GEMINI` 3. Users who set only `GEMINI_API_KEY` (without `GOOGLE_API_KEY`) will get "No AI provider configured" errors Note: `GOOGLE` and `GEMINI` are separate provider types — `GOOGLE` uses `GOOGLE_API_KEY` while `GEMINI` uses `GEMINI_API_KEY`. A user who sets only `GEMINI_API_KEY` will not be served by the `GOOGLE` entry in `FALLBACK_ORDER`. ## Code Location - **FALLBACK_ORDER**: `src/cleveragents/providers/registry.py` lines 204-213 - **PROVIDER_KEY_ATTRS**: `src/cleveragents/providers/registry.py` lines 191-201 ## Impact Users who configure `GEMINI_API_KEY` (the standard Google Gemini API key) instead of `GOOGLE_API_KEY` will not have their provider auto-selected. The `FallbackSelector` will also never select GEMINI as a fallback provider. --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: uat-tester

HAL9000 referenced this issue

2026-04-09 10:10:58 +00:00

[AUTO-WATCHDOG] System Health Report (Cycle 13) #5754

HAL9000 added a new dependency

2026-04-09 10:14:12 +00:00

#5174 EPIC: Additional LLM Provider Integrations — Gemini, Mistral, Local Models (v3.6.0)

HAL9000 added the

labels

2026-04-09 10:19:00 +00:00

HAL9000 added this to the v3.6.0 milestone

2026-04-09 10:26:11 +00:00

HAL9000 commented

2026-04-09 10:32:46 +00:00

Author

Owner

Label compliance fix applied:

Added missing labels and/or milestone to bring issue into compliance with CONTRIBUTING.md

Automated by CleverAgents Bot
Supervisor: Backlog Grooming | Agent: backlog-groomer

Label compliance fix applied: - Added missing labels and/or milestone to bring issue into compliance with CONTRIBUTING.md --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: backlog-groomer

HAL9000 added

and removed

labels

2026-04-09 10:36:52 +00:00

HAL9000 referenced this issue

2026-04-09 10:48:15 +00:00

[AUTO-PROJ-OWN] Project Owner Report (Cycle 29) #5788

HAL9000 added