[Feature Request] Multi-key in one profile to keep the highest availability #1759
neipor
started this conversation in
1. Feature requests
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Is your feature request related to a problem? Please describe.
Yes. Currently, the tool only supports a single API key per profile. When this key hits its usage limit (e.g., free quota exhausted, insufficient credit, or rate limiting by the provider), the AI assistant stops working.
To resolve this, I have to manually go into the settings and replace the exhausted key with a new, valid one. This process is disruptive, interrupts my workflow, and reduces productivity, as I need to pause my coding to perform this manual maintenance.
Describe the solution you'd like
I propose allowing users to add multiple API keys to a single configuration profile.
When the currently active key fails a request due to a quota, credit, or permission-related error, Kilo Code should automatically and seamlessly switch to the next key in the list and retry the request. This process would continue until a working key is found or all keys have been tried.
This would create an automatic failover system for API keys, ensuring the highest possible availability of the service without manual intervention.
Describe alternatives you've considered
The only alternative at the moment is to manually monitor key usage and swap them out when they stop working. This is inefficient and leads to a poor user experience, especially during focused work sessions.
Additional context
Implementing this feature would significantly enhance the reliability and user experience of Kilo Code. It would be particularly valuable for:
Users who rely on multiple free-tier keys to maximize their usage.
Heavy users who might quickly exhaust the limits of a single key.
This would make Kilo Code a more robust and "set-it-and-forget-it" tool, allowing users to focus on coding rather than managing API keys.
Beta Was this translation helpful? Give feedback.
All reactions