Update Gemini 3.1 Pro

[ngoiyaeric]

Add Gemini 3.1 Pro to the main model's available on the system

[ngoiyaeric]

@coderabbitai plan

[coderabbitai]

Coding Plan

Summary

• Extend the existing Gemini integration pattern by adding a new switch case in getModel() for Gemini 3.1 Pro
• Reuse the existing GEMINI_3_PRO_API_KEY environment variable since Google API keys work across model versions
• Add the new model to the UI selection array with consistent styling to the existing Gemini entry
• No changes needed to the geospatial tool since it already checks includes('gemini') which will match the new model

Design Choices

Design Choice 1: API Key Configuration Strategy

Options Considered:

1. Create a new GEMINI_3_1_PRO_API_KEY env var following the version-specific naming pattern
2. Reuse the existing GEMINI_3_PRO_API_KEY since Google keys work across models

Chosen Option: 2

Rationale: Reuse GEMINI_3_PRO_API_KEY to avoid unnecessary key duplication and simplify configuration, as Google API keys are not model-version-specific.

Design Choice 2: Model API Identifier String

Options Considered:

1. Use gemini-3.1-pro-preview (following the pattern of using dots for minor versions)
2. Use gemini-3-1-pro-preview (replacing dots with hyphens for consistency)

Chosen Option: 1

Rationale: Use gemini-3.1-pro-preview as it follows Google's typical model versioning convention with dot notation for minor versions.

💡 User Tips

Regenerate the plan with different choices with @coderabbitai <feedback>.

Implementation Steps

Phase 1: Backend Model Registration

Register Gemini 3.1 Pro in the model resolution system so it can be instantiated when selected by users.

Add Model Case to getModel Function

Extend the model selection switch statement to handle Gemini 3.1 Pro.

• Update lib/utils/index.ts to add a new case 'Gemini 3.1 Pro' in the switch (selectedModel) block
• Use the existing GEMINI_3_PRO_API_KEY env var (already read into gemini3ProApiKey variable)
• Instantiate using createGoogleGenerativeAI({ apiKey: gemini3ProApiKey }) and call with model ID 'gemini-3.1-pro-preview'
• Follow the same error handling pattern as the existing Gemini 3 case when API key is missing

🤖 Prompt for AI agents

Extend the `getModel()` function in `lib/utils/index.ts` to support Gemini 3.1
Pro by adding a new switch case, following the same pattern used for the
existing Gemini 3 integration.

- In the `switch (selectedModel)` block, add a new case for `'Gemini 3.1 Pro'`
- Reuse the existing `gemini3ProApiKey` variable (sourced from
`GEMINI_3_PRO_API_KEY` env var) — do NOT introduce a new env var
- Instantiate the model using `createGoogleGenerativeAI({ apiKey:
gemini3ProApiKey })` and invoke it with the model ID `'gemini-3.1-pro-preview'`
- Apply the same error handling pattern used in the existing Gemini 3 case for
when the API key is missing

Phase 2: Frontend Model Integration

Add Gemini 3.1 Pro to the user-facing model selection interface.

Add Model to Selection Form

Add Gemini 3.1 Pro as a selectable option in the settings UI.

• Update components/settings/components/model-selection-form.tsx to add a new entry to the models array
• Use id: "Gemini 3.1 Pro" (must match the case string in getModel)
• Set appropriate name, description, and badge fields (e.g., badge: "Latest" or "New")
• Use the Sparkles icon to maintain visual consistency with Gemini 3
• Use badgeVariant: "secondary" to indicate it's a new addition

🤖 Prompt for AI agents

Add Gemini 3.1 Pro as a selectable option in the settings UI by updating the
models array in `components/settings/components/model-selection-form.tsx`.

- Add a new entry to the `models` array with the following fields:
- `id: "Gemini 3.1 Pro"` — this must exactly match the case string added in
`getModel()`
- `name`, `description`, and `badge` fields set appropriately (e.g., `badge:
"Latest"` or `badge: "New"`)
- Use the `Sparkles` icon to maintain visual consistency with the existing
Gemini 3 entry
  - Use `badgeVariant: "secondary"` to indicate it is a new addition

Research

The codebase uses a centralized model resolution pattern where lib/utils/index.ts contains a getModel() function that maps user-facing model names to actual provider SDK calls. Models available for user selection are defined in components/settings/components/model-selection-form.tsx as an inline array. The existing Gemini 3 integration uses @ai-sdk/google SDK with createGoogleGenerativeAI, mapping the display name "Gemini 3" to the API model ID gemini-3-pro-preview. Environment variables follow the <MODEL_DESCRIPTOR>_API_KEY naming pattern.

---

🚀 Next Steps

🤖 All AI agent prompts combined

Task: 1

Extend the `getModel()` function in `lib/utils/index.ts` to support Gemini 3.1
Pro by adding a new switch case, following the same pattern used for the
existing Gemini 3 integration.

- In the `switch (selectedModel)` block, add a new case for `'Gemini 3.1 Pro'`
- Reuse the existing `gemini3ProApiKey` variable (sourced from
`GEMINI_3_PRO_API_KEY` env var) — do NOT introduce a new env var
- Instantiate the model using `createGoogleGenerativeAI({ apiKey:
gemini3ProApiKey })` and invoke it with the model ID `'gemini-3.1-pro-preview'`
- Apply the same error handling pattern used in the existing Gemini 3 case for
when the API key is missing
===============================================================================

Task: 2

Add Gemini 3.1 Pro as a selectable option in the settings UI by updating the
models array in `components/settings/components/model-selection-form.tsx`.

- Add a new entry to the `models` array with the following fields:
- `id: "Gemini 3.1 Pro"` — this must exactly match the case string added in
`getModel()`
- `name`, `description`, and `badge` fields set appropriately (e.g., `badge:
"Latest"` or `badge: "New"`)
- Use the `Sparkles` icon to maintain visual consistency with the existing
Gemini 3 entry
  - Use `badgeVariant: "secondary"` to indicate it is a new addition

💡 Iterate on the plan with: @coderabbitai <feedback>

Example Feedback
- `@coderabbitai` You can skip phase 3. Add a simple unit test case for phase 2.
- `@coderabbitai` For design choice 1 go ahead with option 3 and replan.

---

💬 Have feedback or questions? Drop into our discord!