Hey everyone!
I’ve noticed something lately about how “Usage Events” are being counted, specifically concerning “Included Requests.” I wanted to check if others are seeing this too, and if it’s a bug or if I’m misunderstanding something.
Basically, it seems like if the AI responds, but I don’t use it (I abort the generation), or if the AI itself errors out, these actions are still consuming my “Included Requests” quota!
You can take a look at the screenshots I’ve attached:
- Check out my Overview page (attached images 2.png and 4.png): You can see my “Included Requests” counter increasing (e.g., from 124/500 to 125/500), which means my quota is being used up.
- Now look at my “Usage Events” list (attached image 1.png, and the highlighted part in image 3.png):
- If the AI successfully generates code and I accept it (showing “Included in Pro”), that’s totally fine and expected to count. No issues there.
- But here’s the key: In attached image 3.png, I’ve highlighted an entry that says “Aborted, Not Charged.” This action (where I explicitly stopped the AI, and it wasn’t charged) is still clearly logged as a “Usage Event”! The AI didn’t give me any useful output, and I didn’t even use it, so why is it taking up a request?
- Also, I want to mention that I’ve seen “Errored, Not Charged” entries in my usage history as well. For instance, I recall specific error entries like “Jun 19, 07:55 PM You Errored, Not Charged” and “Jun 19, 07:54 PM You Errored, Not Charged.” While I can’t provide screenshots for those particular instances, they were counted towards my total requests at the time.
My main question and what I’d like to discuss with everyone is:
- Have any of you encountered similar situations? Are “Aborted” or “Errored” AI responses consuming your “Included Requests” quota?
- Do you think this is a bug in Cursor, or is this the intended new counting logic?
I remember in older Cursor versions, only successful and accepted AI interactions would count towards the request limit. This new behavior seems a bit unusual.
I hope this discussion helps us all understand the current counting logic better, and perhaps provides valuable feedback for the Cursor team to optimize the user experience and billing transparency.
Thanks everyone for your time!
