Cursor agents not working

Where does the bug appear (feature/product)?

Cloud Agent (GitHub, Slack, Web, Linear)

Describe the Bug

Cursor agents are not working, 9 out of 10 times they fail with an error continuously for days now.

Steps to Reproduce

Start an agent

Operating System

Windows 10/11

Version Information

Version: 3.17.21 (user setup)
VS Code Extension API: 1.128.0
Commit: 8f2a112cb2845a97b75fd932ea5c470579ca4060
Date: 2026-08-25T01:05:08.089Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.291
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

Yes - Cursor is unusable

Update: I’m using the desktop app, I accidentally selected cloud.

Hey, thanks for the report. What you’re seeing is High Load, and it’s caused by load on the model, not by your setup.

Grok 4.6 is under very high demand right now, and during peak hours (roughly morning to noon in Europe) some requests fail with an error instead of running. We’re tracking this, and capacity is being expanded over time.

For now, these usually help:

  • Retry the request in a few minutes, it often goes through.
  • Switch the agent to a different model, like Auto or Grok 4.5, this avoids peak windows completely.

If agents keep failing outside those peak hours, send me the Request ID from the failed run (in chat: top right menu > Copy Request ID) and I’ll take a closer look. Also, about the post above, since you’re on the desktop app, you can ignore the Cloud Agent selection, it doesn’t affect this issue.