fix: HOTFIX gemini model add form

[RomneyDa]

Description

Nonexistent value for gemini 2.5 pro exp was breaking selector
Fixes #8896, #8846, #8893, #8880, #8943, #8932, #8946, #8947

Let's fix types on this soon so doesn't happen again

---

Summary by cubic

Fixed the Add New Model selector by removing the nonexistent “Gemini 2.5 Pro Exp” option from the Gemini provider list. This prevents the form from breaking when choosing a Gemini model.

^{Written for commit bc6f599. Summary will update automatically on new commits.}

[continue]

Keep this PR in a mergeable state →

Learn more

---

All Green is an AI agent that automatically:

✅ Addresses code review comments

✅ Fixes failing CI checks

✅ Resolves merge conflicts

[continue-development-app]

Keep this PR in a mergeable state →

Learn more

---

All Green is an AI agent that automatically:

✅ Addresses code review comments

✅ Fixes failing CI checks

✅ Resolves merge conflicts

[continue-development-app]

Keep this PR in a mergeable state →

Learn more

---

All Green is an AI agent that automatically:

✅ Addresses code review comments

✅ Fixes failing CI checks

✅ Resolves merge conflicts

[github-actions]

✅ Review Complete

Code Review

This is a straightforward hotfix that removes a nonexistent model reference (models.gemini25ProExp) from the Gemini provider configuration. The change fixes the Add New Model selector that was breaking when users tried to select a Gemini model.

✅ Overall Assessment: This fix is appropriate and addresses the immediate issue.

Observations:

1. Root Cause: The PR removes a model reference that doesn't exist in the models configuration, which was causing the selector to break. This is the right immediate fix.

2. Missing Investigation: The PR doesn't show where models.gemini25ProExp was supposed to be defined. Before merging, verify:

   • Was this model definition removed elsewhere?
   • Or was it never properly added?
   • Check models object definition to ensure consistency

3. Type Safety (as noted in PR description): The fact that this nonexistent reference didn't cause a build-time error suggests missing type checking. Consider:

   • Adding stricter TypeScript checks on the providers.ts configuration
   • Using a type-safe enum or const assertion for model references
   • Adding a build-time validation that all referenced models exist

4. Testing: Consider adding:

   • A unit test that validates all provider model references exist in the models configuration
   • Basic smoke test for the Add New Model form with Gemini provider

Suggested Follow-up (separate PR):

// Example validation to prevent this issue:
const validateProviderModels = () => {
  providers.forEach(provider => {
    provider.models.forEach(model => {
      if (!model.model) {
        throw new Error(`Invalid model reference in ${provider.provider}`);
      }
    });
  });
};

The fix itself is correct for a hotfix. The multiple related issues (#8896, #8846, #8893, #8880, #8943, #8932, #8946, #8947) suggest this was causing significant user impact, so shipping this quickly makes sense.

---

[continue]

Reviewed PR #8954. No documentation updates needed.

This is a clean bugfix that removes a non-existent model variant (gemini25ProExp) from the Add New Model form dropdown. The existing documentation references are:

• Gemini 2.5 Pro (not "Exp") - a valid model with hub link at https://hub.continue.dev/google/gemini-2.5-pro
• Documentation shows manual configuration via Mission Control, which is unaffected by this UI dropdown change
• No docs reference the removed experimental variant

The fix correctly unbreaks the form without requiring any documentation changes.

[cubic-dev-ai]

No issues found across 1 file

[sestinj]

🎉 This PR is included in version 1.33.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[sestinj]

🎉 This PR is included in version 1.8.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[sestinj]

🎉 This PR is included in version 1.37.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[sestinj]

🎉 This PR is included in version 1.7.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀