More OpenAI configurability

[KTibow]

Check for existing issues

• Completed

Describe the feature

tl;dr I'd like a way to remove models and possibly use separate APIs and reorder models

For context, if you reconfigure your OpenAI base URL, the models get really pushed down. You also can't have two different OpenAI base URLs.

Continue to the mockup section for some of my ideas.

Environment

Zed: v0.165.4 (Zed)
OS: Linux Wayland fedora 40
Memory: 15.2 GiB
Architecture: x86_64
GPU: Intel(R) Iris(R) Plus Graphics (ICL GT1.5) || Intel open-source Mesa driver || Mesa 24.1.7

If applicable, add mockups / screenshots to help present your vision of the feature

So the main thing I'd like is a way to disable models that are unneeded.
There's a few ways this could work:

• A configuration setting like

  "use_default_models": false,

  (this applies in the case that you configured OpenAI so the "gpt-4o", "gpt-3.5-turbo", etc models are broken)
• A configuration setting like

  "model_order": ["Claude 3.5 Sonnet", "Llama", "GPT-4o"]

  This has the bonus of allowing reordering of models.
• A section in the "Configuration" GUI
  This would look like the existing model chooser but with x or - buttons to remove models.
  This could have the bonus of allowing reordering of models if dragging was enabled.

The second thing I'd like is to allow multiple URLs. This could look like

  "language_models": {
    "openai": {
      "available_models": [
        {
          "name": "llama-3.3-70b-specdec",
          "display_name": "Llama",
          "max_tokens": 6000,
          "api_url": "https://api.groq.com/openai/v1/"
        },
        {
          "name": "gpt-4o",
          "display_name": "GPT-4o",
          "max_tokens": 16000,
          "api_url": "https://api.openai.com/v1/"
        }
      ]
    }
  }

or it could look like

  "language_models": {
    "openai": {
      "version": 2,
      "api_urls": ["https://api.openai.com/v1/", "https://api.groq.com/openai/v1/"]
    }
  }

The first version would have you configure every model you want to use. The second version would have Zed fetch all available models using the models endpoint, and ask you to remove the ones you don't want with the previous model removal methods. Both would require Zed to store separate auth tokens for each API URL.

[notpeter]

Being able to configure multiple endpoints/apikeys for the same underlying "provider" is a duplicate of:

• Allow add custom AI assistant provider #15732

As the number of models/providers grows the single monolithic list of models is definitely becoming harder to use. There have been some mocks of alternatives done internally (multiple dropdowns; folding by provider; pinning specific models, hiding models, etc) but we haven't landed on anything specific yet. I'm going go ahead and migrate this to a discussion in case folks have further ideas.

Thanks for reporting.