Cursor error
Cursor: Too Many Requests ... Rate limit exceeded
{"error": "Too Many Requests", "message": "Rate limit exceeded. Please try again later."}Status: By designLast verified 2 documented fixes2 sources
What it means
HTTP 429 from Cursor's APIs: the per-user, per-team or per-organization rate limit was exceeded. Admin and Organization API responses include Retry-After: 60 and the body {"code": "error", "message": "Rate limit exceeded"}.
Causes
- Exceeding the endpoint's limit. Unless an endpoint documents a different limit, the default is 20 requests per minute (for example Admin API most endpoints 20/min, Analytics API most team endpoints 100/min, Bugbot /bugbot/review 30/min).
How to fix it
- Fix 1.
Implement exponential backoff: when you receive a 429, wait before retrying with increasing delays (1s, 2s, 4s, 8s, 16s in the docs' example).
TOMLwait_time = 2 ** attempt time.sleep(wait_time) - Fix 2.
For Admin and Organization APIs, honor the Retry-After: 60 header.
More Cursor errors
All 18 Cursor errorsAgent Execution Timed OutStatus: WorkaroundTimeout waiting for EverythingProviderStatus: Workaround<filename> is too large (4MB limit)Status: By designCursor is damagedStatus: Workaroundsuspicious activityStatus: Workaroundxcrun: error: unable to find utility "mcpbridge"Status: Workaroundmissing tabIdentifierStatus: WorkaroundPrivate worker limit exceededStatus: By design
Related reading
- Do Your Agent Hooks Fail Open? Claude Code vs Codex vs Cursor vs Gemini CLIA guard hook that crashes, times out or points at a missing script lets the tool call through by default in Claude Code. v2.1.295 adds onFailure: block. Here is what each coding agent does when your policy hook breaks, with real test runs.
- How to Keep API Keys Away From Your AI Coding Agent: Claude Code vs Codex vs Cursor vs Gemini CLIA deny rule on .env stops cat but not a Python one-liner. Here are the three layers that actually keep secrets out of a coding agent's context - file rules, environment scrubbing and credential masking - and what Claude Code, Codex, Cursor and Gemini CLI give you for each, with real test runs.
- Antigravity vs Cursor (2026): Pricing, Limits, Models, and Which to PickAntigravity vs Cursor: Antigravity is free with a weekly limit; Cursor starts at $20/month with the widest model menu. Pricing, limits and a decision guide.
- Slack Code vs Claude Code vs Cursor vs OpenCode: When Agents Belong in ChatSlack Code gives coding agents their own Slack channels with diffs, previews, and an audit log. When it beats Claude Code, Cursor, or OpenCode, and when not.
- Cursor Removes Dollar Costs From Usage Page: Tokens OnlyCursor removed dollar costs from its Usage page on July 31: self-serve plans see tokens only and the dashboard API zeroes cost fields, history included.
- AI Coding Agent Security Models Compared 2026: Permissions, Sandboxing, and Threat Models for Every Major ToolAI coding agent security models compared: how Claude Code, Cursor, Codex, Copilot, Aider and Windsurf handle permissions, sandboxing and prompt injection.
FAQ
What does "Too Many Requests ... Rate limit exceeded" mean in Cursor?
HTTP 429 from Cursor's APIs: the per-user, per-team or per-organization rate limit was exceeded. Admin and Organization API responses include Retry-After: 60 and the body {"code": "error", "message": "Rate limit exceeded"}.
How do I fix "Too Many Requests ... Rate limit exceeded"?
There are 2 documented fixes. Start with the first: Implement exponential backoff: when you receive a 429, wait before retrying with increasing delays (1s, 2s, 4s, 8s, 16s in the docs' example).
Is this Cursor error fixed?
Status: By design. Expected behavior, not a bug. The documented fixes change the setup that triggers it.
Sources
Last verified against 2 sources: official docs, maintainer replies and release notes.
Newsletter
Fixes for the tools you use, weekly
One email per week. New coding agent releases, what broke, and how developers are working around it.