Skip to content

Split out openai-gpt gpts into different agents #348

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
StevenBucher98 opened this issue Mar 3, 2025 · 0 comments
Open

Split out openai-gpt gpts into different agents #348

StevenBucher98 opened this issue Mar 3, 2025 · 0 comments
Labels
Issue-Enhancement The issue is a feature or idea

Comments

@StevenBucher98
Copy link
Collaborator

StevenBucher98 commented Mar 3, 2025

Summary of the new feature / enhancement

As a user I want to switch between different openAI compatible AI providers in a similiar way that I switch between agents using the @ sign. It is confusing to treat them as different "GPTs" under the "openAI" agent especially if I call a different provider entirely like Google Gemini or DeepSeek.

Proposed technical implementation details (optional)

Ability to switch to different GPTs via the @ sign. For example if I have the following GPTs configured

{
    "GPTs": [
        {
          "Name": "deepseek",
          "Description": "A GPT instance using DeepSeek v3.",
          "Endpoint": "https://api.deepseek.com",
          "ModelName": "deepseek-chat",
          "Key": "<your-deepseek-api-key>",
          "SystemPrompt": "You are a helpful assistant."
        },

        {
          "Name": "gemini",
          "Description": "A GPT instance using Google Gemini.",
          "Endpoint": "https://generativelanguage.googleapis.com/v1beta/openai/",
          "ModelName": "gemini-1.5-flash",
          "Key": "<your-gemini-api-key>",
          "SystemPrompt": "You are a helpful assistant."
        }
    ]

    "Active": "deepseek"
}

It is unclear to users unfamiliar with the concept of GPTs to have to do @OpenAI-GPT agent and then /gpt use gemini to switch between these different providers. It may make more sense to do @gemini or @deepseek so user has a more clear indicator of what the currently called GPT is in the prompt rather than just at the beginning.

I'd also be open to using some kind of dot notation like @openai.gemini but personally feel typical user is not going to be familiar with GPTs. Open to discussion on this, I think I rather the @ notation.

@StevenBucher98 StevenBucher98 added the Issue-Enhancement The issue is a feature or idea label Mar 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Enhancement The issue is a feature or idea
Projects
None yet
Development

No branches or pull requests

1 participant