← All errors · CursorCursor editor & agent errors
High Load: We're experiencing high demand for this model
Exact error
{"error":"ERROR_RESOURCE_EXHAUSTED","details":{"title":"High Load","detail":"We're experiencing high demand for Composer 2.5 right now. Please switch to Auto, another model, or try again in a few moments.","isRetryable":true}}What it means
Cursor's backend temporarily has no spare capacity for the specific model you selected (often Composer). Each Agent step is a separate model call, so this can interrupt a run that already started editing.
Likely causes
- High demand for that exact model at the moment of the request.
- A long Agent turn making many sequential model calls during a capacity spike.
- Not an account, VPN, or project-config problem in most cases.
How to fix it
Switch the model dropdown to Auto (or another available model) and retry the same prompt. Prefer picking Auto from the dropdown rather than relying on a banner button.
Wait one or two minutes and retry if you want to stay on the same model — the error is marked retryable.
If the Agent already edited files, review the diff / use checkpoints or git before re-running so you do not double-apply partial changes.
Check the Cursor status page for an active incident if every model fails.
Prevent this next time
- Commit before letting the agent make large changes so you can always roll back.
- Put recurring instructions in project rules instead of repeating them in chat.
FAQ
What does "High Load: We're experiencing high demand for this model" mean?
Cursor's backend temporarily has no spare capacity for the specific model you selected (often Composer). Each Agent step is a separate model call, so this can interrupt a run that already started editing.
What usually causes it?
High demand for that exact model at the moment of the request. A long Agent turn making many sequential model calls during a capacity spike. Not an account, VPN, or project-config problem in most cases.
How do I fix it?
1. Switch the model dropdown to Auto (or another available model) and retry the same prompt. Prefer picking Auto from the dropdown rather than relying on a banner button. 2. Wait one or two minutes and retry if you want to stay on the same model — the error is marked retryable. 3. If the Agent already edited files, review the diff / use checkpoints or git before re-running so you do not double-apply partial changes. 4. Check the Cursor status page for an active incident if every model fails.
Related errors
- Cursor: model is overloaded / slow requests
- Cursor: Connection failed. Check your internet connection or VPN
- Cursor agent keeps making the same failed edit
Get new fixes weekly
No spam. Unsubscribe anytime. Privacy