Unique API Key for each API Config Profile

[Triquetra]

As currently implemented, it seems that the API Config Profile uses a single API Key per provider. This design introduces limitations on the use of Kilo Code. The following 2 use cases are issues I have personally encountered that could be resolved by allowing unique keys for each API Config Profile:

1. Codestral is available for free through Mistral. But using the free Codestral API requires a separate key from using Mistral's other models. Given the current API Key handling implementation, this effectively means that the user must choose between using Codestral Free or other Mistral models - but not both. This would be solved by allowing each API Config Profile to have its own key. So 2 Mistral profiles could be created: one for Codestral, and one for other models.

2. Requesty allows customization per API key for things like fallback, load balancing, and some other features. But because Kilo Code currently only allows one key per provider, this Requesty feature cannot be utilized. Allowing different keys per API Config profile would permit this Requesty feature to be used.

One advantage of the current implementation is the lack of need to re-enter keys, but a separate index could be created for each provider to manage keys input through Kilo Code. The UI could then permit the user to select from already entered keys for the currently selected provider or enter a new one. Thus, getting the best of both worlds.

[Juice10]

I think we might be going in a direction that gets you even further away from what you are trying to accomplish here. But this is important context to have, thank you for sharing Triquetra! Curious how we can do this while keeping the UI user friendly.

[Triquetra]

With this new UI, I think this could be accomplished by allowing different provider profiles. So for my use case, I could create different Requesty provider profiles for each key. Or 2 Mistral provider profiles; one that provides the Codestral model, and another with the other key that provides the other models.

[piknockyou]

This functionality is already available. You can add different API keys for the same provider by creating separate profiles. For instance, I have two Gemini CLI OAuths and three different Gemini API keys configured through various profiles.

[Triquetra]

This functionality is already available. You can add different API keys for the same provider by creating separate profiles. For instance, I have two Gemini CLI OAuths and three different Gemini API keys configured through various profiles.

Are you using VSCode or VSCodium? Because it seems that they store the API key per provider, not per profile.

[piknockyou]

Void Editor

[piknockyou]

I may be late to this discussion, but it appears the feature you requested might have already been implemented. According to the documentation, you can configure different settings for each profile, including separate API keys.

Have you tried creating multiple profiles? Simply create a new profile with a different name but the same provider, then enter a different API key. When you test both profiles, you should find that it works seamlessly.

Since my last messages, I've successfully set up multiple API keys from the same provider using different profiles. Could you please confirm whether this approach works for your use case?