A user uses a personal API token and tries to ask Cursor a question. Cursor fires off API calls so rapidly that the API token becomes rate‑limited for the next minute, and Cursor then replies to the user with an error.
Cursor should be able to dynamically handle these rate‑limiting errors and adjust. Does it need to know the tiers of API tokens or their limits? No. It just needs to finish that agent query using the internal API token and alert the user that the rest of the query will be sent through the internal token.
Right now I’m hesitant to use my API token because Cursor is unable to handle rate limiting. I think this is a high‑priority and easy fix for Cursor to implement.