Home / Guides / Cursor Rate Limits
Cursor Rate Limits Explained
Everything you need to know about Cursor rate limits - the 500 fast-request cap, automatic slow-mode fallback, premium-model quotas, and how to never get caught off guard.
Last updated April 2026 · By Soren Starck
What Are Cursor Rate Limits?
Cursor doesn't lock you out - it slows you down. Every Pro plan gets 500 fast requests per month. Past 500, requests still work, but they go to the unprioritized queue and take 5–30+ seconds each instead of 1–3.
Plan Comparison
| Plan | Fast requests / month | Slow requests | Premium models |
|---|---|---|---|
| Hobby (free) | 50 (one-time) | Unlimited | Limited preview |
| Pro ($20/mo) | 500 | Unlimited | Capped premium quota |
| Pro+ ($40/mo) | 2,000+ | Unlimited | Larger premium quota |
| Business / Enterprise | Per-seat allocation | Unlimited | Per-seat premium |
Numbers shift as Cursor iterates plans, so the dashboard is always the source of truth. The pattern doesn't change: fast caps + slow fallback + premium-model quotas on top.
What Happens When You Hit the Limit
- Slow mode kicks in silently - no popup, no warning
- Latency jumps 5–10x - what took 2 sec now takes 15
- Tab autocomplete still works, but composer/agent flows feel sluggish
- Premium-model quota exhaustion just blocks those models - no fallback
- Lost flow - you start blaming your laptop or the network before realizing
SessionWatcherSlow mode happens silently.
SessionWatcher catches it first.
Native macOS menu bar app. Track Claude and Codex usage, costs, and rate limits in real-time.
“Fast, simple, and does exactly what it should. Definitely worth it.”
@nicojerome on GitHub
macOS 14+. $2.99 one-time purchase.
How to Monitor Cursor Rate Limits
SessionWatcher for Cursor watches your fast-request count, slow-mode threshold, and premium-model quota live in your macOS menu bar.
- Fast requests remaining - exact count, no refresh needed
- Burn-rate projection - at this pace, slow mode hits on day X
- Premium model breakdown - how much of each model's quota is left
- Billing-cycle countdown - exact day of monthly reset
- macOS notifications - at 80% and 95%
Tips for Managing Cursor Rate Limits
- Reserve fast requests for composer/agent - Tab autocomplete is cheaper to feel slow on.
- Use base models for grunt work - premium quota disappears fast on Opus / o1.
- Watch burn rate, not just totals - 250 by day 10 means slow mode by day 20.
- Time heavy refactors for early in the cycle, lighter cleanup later.
- Set 80% notifications so you can decide: pace, upgrade, or cool down.
Frequently Asked Questions
What are Cursor rate limits?
Pro caps fast requests at 500/month. Past that, slow mode (unlimited but slower). Premium models have separate caps on top.
How long until my Cursor fast requests reset?
They reset on your billing cycle date. SessionWatcher tracks the exact countdown.
How do I avoid hitting Cursor rate limits?
Track burn rate live with SessionWatcher ($2.99 one-time). 80%/95% notifications give you time to pace before slow mode hits.