Fast Request Count Inaccurate — Wrongly Moved to Slow Pool

Describe the Bug

Summary:
This morning, my account was unexpectedly throttled to the slow request pool. When I last checked, I had only used 63 out of 500 fast requests. After contacting [email protected], the automated chatbot claimed I had used 563 requests, which is a sudden and unexplained jump.

Details:

I manually reviewed my usage from June 11 to June 17.

Total number of valid requests: 163 — including multiple failed/errored attempts.

I sent a second email to clarify, and the chatbot then claimed 600 requests used, further increasing the count with no usage in between.

Steps to Reproduce

its not client side

Expected Behavior

The system should:

Accurately track and display the number of fast requests used.

Exclude failed or errored requests from the count.

Show consistent and transparent request data.

Operating System

Linux

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.1.2
VSCode Version: 1.96.2
Commit: 87ea1604be1f602f173c5fb67582e647fcef6c40
Date: 2025-06-13T00:28:07.271Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Linux x64 6.11.0-26-generic

Does this stop you from using Cursor

No - Cursor works, but with this issue

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.