Describe the Bug
There is a mismatch between the number of total requests used (250/500 shown in the dashboard) and the analytics report (which only shows the actual 112 requests from June 4–13). Additionally, fast requests are not being properly renewed at the start of each billing cycle. This issue has been recurring across multiple months (April, May, June). Despite having unused fast requests, Cursor did not renew the 500-request allowance correctly, leading to shortage of fast requests I can use per month.
Steps to Reproduce
- Wait until a new billing cycle starts (4th of the month).
- Observe that fast requests do not reset on the 1st, but instead reset on the 4th.
- During this window (4th), run fast requests – they still execute, but they don’t count against a renewed allowance.
- When requests are finally renewed on the 4th, the full 500 fast requests are not available.
- Compare “Included Requests” count to the request count shown in the Analytics chart — they don’t match.
Expected Behavior
- Fast requests should reset at the beginning of the billing cycle June 4th.
- The usage shown in the top-level request counter should match the actual request count in the analytics dashboard.
- Any unused fast requests should be counted to next month, not disappear or be miscounted.
Screenshots / Screen Recordings
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Cursor: Version 1.0.0 (Universal)
VSCode Base: Version 1.96.2
Electron: 34.5.1
Node.js: 20.19.0
Chromium: 132.0.6834.210
Additional Information
This discrepancy and inflation in fast request counts also happened in May and April. Despite having unused fast requests at the end of the month, they didn’t renew properly. Cursor let me use remaining requests from the previous month, but it did not reset the full 500 when the new billing cycle started.
Does this stop you from using Cursor
Sometimes - I can sometimes use Cursor