Skip to content

[Feature] [Gemini] Implement Full Google Gemini API Support (UI + Backend) #62

@HexdoAI

Description

@HexdoAI

Parent Epic: #56
Depends on: #61 (This issue introduces the "Provider Type" UI)

🎯 Goal

Implement end-to-end support for the Google Gemini API, allowing users to add it as a custom model provider.

💻 UI Requirements (Frontend)

  1. Add "Gemini" as an option to the "Provider Type" dropdown menu (introduced in [Feature] [Azure] Implement Full Azure OpenAI Support (UI + Backend) #61).
  2. When a user selects "Gemini", the form must show the following fields:
    • API Key
    • API Address (Optional: Allow users to specify a custom/proxy endpoint instead of the default generativelanguage.googleapis.com)

⚙️ Backend Requirements

  1. Modify the "save model" API to store the provider_type: 'Gemini' and its associated fields.
  2. The backend logic must check the provider_type for the model.
  3. If the provider_type is "Gemini", the system must route the API call to the llm.gemini.js client (this client may need to be created or updated).
  4. The llm.gemini.js client must correctly use the API Key and target the API Address (or the default Gemini endpoint if not provided) to make successful API requests.

✅ Acceptance Criteria

  • A user can successfully add and save a Gemini API configuration via the UI.
  • The system can use this configuration to successfully make calls to the Gemini API.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No fields configured for Feature.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions