Skip to content

fix: rename gemini provider from 'geminiai' to 'google' to match backend#289

Open
cbeatty8 wants to merge 1 commit intogenlayerlabs:mainfrom
cbeatty8:fix/gemini-provider-name
Open

fix: rename gemini provider from 'geminiai' to 'google' to match backend#289
cbeatty8 wants to merge 1 commit intogenlayerlabs:mainfrom
cbeatty8:fix/gemini-provider-name

Conversation

@cbeatty8
Copy link
Copy Markdown

@cbeatty8 cbeatty8 commented Mar 29, 2026

Fixes #271

Problem

When running genlayer init and selecting Gemini as the LLM provider, initialization fails with:

Error: Requested providers {geminiai} do not match any stored providers.

Root Cause

  • CLI sends: geminiai
  • Backend expects: google

Verified in genlayer-studio:

  • backend/node/create_nodes/default_providers/google_gemini-*.json: "provider": "google"
  • tests/integration/test_llm_providers_registry.py: "google": "GEMINI_API_KEY"
  • frontend/src/assets/schemas/providers_schema.json: enum includes "google"

Changes

  • Rename provider key from geminiai to google in AI_PROVIDERS_CONFIG
  • Update AiProviders type to use google instead of geminiai
  • cliOptionValue now sends google to match backend expectations

Files Changed

  • src/lib/config/simulator.ts (3 lines)

Summary by CodeRabbit

  • Chores
    • Updated the AI provider identifier used in configuration and CLI from "geminiai" to "google".
    • The provider will continue to display as "Gemini" and the existing Gemini environment variable remains unchanged.
    • This adjusts provider selection and CLI option mapping to use the new identifier.

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Mar 29, 2026

Warning

Rate limit exceeded

@cbeatty8 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 23 minutes and 15 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 23 minutes and 15 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 430ab265-d8da-4f42-b9c8-c8090ddf65e0

📥 Commits

Reviewing files that changed from the base of the PR and between 0a0fa48 and cfdf8b6.

📒 Files selected for processing (1)
  • src/lib/config/simulator.ts
📝 Walkthrough

Walkthrough

The provider identifier for Gemini was changed from geminiai to google in src/lib/config/simulator.ts, updating the AiProviders type and the AI_PROVIDERS_CONFIG entry while keeping the display name and environment variable unchanged.

Changes

Cohort / File(s) Summary
Provider Configuration Update
src/lib/config/simulator.ts
Replaced geminiai with google in the exported AiProviders union type and updated the AI_PROVIDERS_CONFIG entry to use cliOptionValue: "google" (display name: "Gemini" and envVar: "GEMINI_API_KEY" unchanged).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 I hopped through code at break of day,
Swapped a name that led astray,
From geminiai to google clear,
Now Gemini whispers in the right ear,
A tiny fix, a joyful cheer!

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: renaming the gemini provider identifier from 'geminiai' to 'google' to align with backend expectations.
Linked Issues check ✅ Passed The PR fully addresses the linked issue #271 by changing the provider identifier from 'geminiai' to 'google' in both the type definition and configuration, matching the backend's expected value.
Out of Scope Changes check ✅ Passed All changes are directly scoped to fixing the Gemini provider name mismatch issue; no unrelated modifications are present in the changeset.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@cbeatty8 cbeatty8 force-pushed the fix/gemini-provider-name branch from a13c4ba to 0a0fa48 Compare March 29, 2026 02:54
Fixes genlayerlabs#271

The backend's llm_provider table uses 'google' for Gemini provider,
but the CLI was sending 'geminiai'. This caused init to fail with:
'Requested providers {geminiai} do not match any stored providers.'

Changes:
- Rename provider key from 'geminiai' to 'google' in AI_PROVIDERS_CONFIG
- Update AiProviders type to use 'google' instead of 'geminiai'
- cliOptionValue now sends 'google' to match backend expectations
@cbeatty8 cbeatty8 force-pushed the fix/gemini-provider-name branch from 0a0fa48 to cfdf8b6 Compare March 29, 2026 02:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Gemini provider initialization fails due to provider name mismatch (geminiai vs google)

1 participant