Cursor Agent stuck or not progressing: causes and fixes
Is there an outage right now?
Cursor official status is operational. If this error persists, it is likely an implementation or environment issue on your side.
Updated: Jul 21, 2026, 11:41 PM UTC
View Cursor status →What this error means
The Agent doesn't respond or stalls mid-run. Causes: Cursor/model outage, rate limits, long tasks, or auth.
Common causes
- •Cursor/model outage or overload
- •Rate limit / quota exceeded
- •Long/large task
- •Auth/subscription issue
- •Unstable network
How to fix
- 1.Wait and re-run
- 2.Split the task
- 3.Restart Cursor
- 4.Re-login / check subscription
- 5.Check outage status at top of page
When waiting helps (and when it won't)
If Cursor/model-side, it recovers over time. If frequent, split tasks or switch model.
Alternatives when Cursor is down
Related symptoms
FAQ
What causes CursorのAgentが止まる?
The Agent doesn't respond or stalls mid-run. Causes: Cursor/model outage, rate limits, long tasks, or auth.
How do I fix CursorのAgentが止まる?
Wait and re-run / Split the task / Restart Cursor / Re-login / check subscription / Check outage status at top of page