// WHAT IT MEANS
A short burst limit — too many requests in a small window — either Cursor's own or passed through from the model provider. It is not your monthly usage pool: that one produces a different message ("You've hit your usage limit") and offers usage-based pricing.
It appears most often during long agent runs with many tool calls, or when several Composer sessions run at once.
// WHEN IT RESETS
Within a few minutes; there is no fixed reset time. Retrying immediately extends the throttle — waiting one to two minutes usually clears it.
Your monthly pool is a different clock: it resets on your billing date, not the first of the month, and Settings → Usage shows the exact day. Cursor has never reset everyone's pool early; its changes are pricing and allowance adjustments, logged below.
// WHAT TO DO NOW
- 01 Wait a minute or two before retrying; do not spam the request.
- 02 If it says "with provider", switch models — the third-party API (Claude, GPT, Gemini) is throttling, and Cursor's first-party models are on a different path.
- 03 Reduce parallelism: one agent session at a time on the same account.
- 04 If the message is actually about your usage limit, Settings → Usage shows both pools (first-party and third-party) and your billing-date reset; usage-based pricing continues work at API rates.
// DOES IT AFFECT MY WEEKLY ALLOWANCE?
Cursor has no weekly allowance — it is monthly, on your billing date, split into a first-party pool and a third-party model pool. A burst limit spends nothing from either.
// ALSO APPEARS AS
- “Rate limit exceeded”
- “You've hit your usage limit”
- “Too many requests”