Add provider-aware model selector with manual entry toggle

[rahulbansal29]

Provider-aware Model Selector in AI Config

Summary

Enhance the AI Configuration UI by introducing preset model lists per provider and replacing the current model input with a single adaptive control:

• Show a dropdown of preset models for supported providers
• Include a “Manual entry…” option to allow custom model input in the same control
• Preserve existing validation rules
• Persist provider and model selection via localStorage

---

Feature Details

Model Selection Control

• Replace the existing model text input with one unified control
• When presets exist for the selected provider:
  • Display a dropdown containing:
    • Preset model options
    • A “Manual entry…” option
• Selecting “Manual entry…”:
  • Switches the dropdown into a text input in the same location
  • User can type a custom model name
• When no presets exist:
  • Default directly to manual text input

---

Validation (Preserve Existing Behavior)

• Model is always required
• API Key
  • Required for all providers except Ollama
• Custom Endpoint
  • Required only for openai-compatible providers
• Validation must work correctly for:
  • Preset model selection
  • Manual model entry

---

Persistence

• Continue saving configuration to localStorage
• Persist:
  • Provider
  • Model (preset or manual)
• On reopening the AI Config modal:
  • Previously selected provider and model must restore correctly
  • Manual or preset selection should remain intact

---

##Video Example

video.sample.mp4

Goal

Provide a flexible yet simple model selection experience that supports both quick preset usage and advanced custom models without adding UI complexity.
Fix #607

[netlify]

✅ Deploy Preview for ap-template-playground ready!

Name	Link
🔨 Latest commit	61b5ced
🔍 Latest deploy log	https://app.netlify.com/projects/ap-template-playground/deploys/696f23addf73990008a249ef
😎 Deploy Preview	https://deploy-preview-608--ap-template-playground.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[JiyaGupta-cs]

@rahulbansal29 Adding fixed model names directly to the dropdown isn’t a good long-term approach. LLM providers deprecate models and introduce new ones very frequently, so hardcoding model names will quickly go stale and is likely to cause 404 errors in the near future.
The current implementation, where we provide example models rather than a fixed list, is more flexible and resilient to provider-side changes.

[rahulbansal29]

@JiyaGupta-cs @Rahul-R79
Thanks for the feedback — that’s a fair concern and I agree with the underlying point.
LLM providers do deprecate and introduce models frequently, and hard-coding model names can definitely go stale and lead to 404s over time. The goal of the dropdown was not to strictly enforce a fixed set of models, but to improve discoverability and UX for new users by surfacing example / commonly used models, while still allowing full flexibility.
That’s why the design includes a “Manual entry…” option, so users can always enter any valid or newly released model without being blocked by the preset list.