Closed howardelton closed 1 week ago
I don't have any plans to add multiple API keys for a single provider, but I highly suggest you use open router to work around these rate limit issues. They will be adding prompt caching soon which would make them the best api option.
The cost, token and caching information provided in the GUI is so incredibly useful. As a developer who is working on multiple projects at the same time, I would like to create a Claude API for each project, so I can see the breakdown of costs on the Anthropic Console for each project (https://console.anthropic.com/settings/usage). The only way to do that now, would be to manually keep changing the API key in the Settings of CLAUDE DEV. I suggest changing the "Anthropic API Key" textbox to a dropdown of multiple API keys displayed with a user definable label for each that could represent each project's name. For example, dropdown option 1 is "Project 1" and so on. This would have the added benefit of not displaying the API key on the screen (only the labels for the keys) unless they are edited somehow. This is also a privacy improvement for people working in environments where they don't want people looking over their shoulder and seeing their API key whenever the developer goes into the settings screen.