Cloud Agent assign fails with GitHub rate limited — user quota is full

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cloud Agent (GitHub, Slack, Web, Linear)

Describe the Bug

Assigning a Cloud Agent to a GitHub issue fails with:

GitHub rate limited: GitHub is rate limiting requests. Please try again later.

My GitHub account is not rate limited. https://api.github.com/rate_limit shows about 5000 of 5000 remaining. gh can read the private repo and the issue. I waited over 3 hours, reset GitHub in Cursor Dashboard → Integrations, and tried again. Same error.

Steps to Reproduce

Steps to Reproduce

Open GitHub issue https://github.com/richamcgill/research-swarm/issues/25
Assign Cursor Cloud Agent
Error appears

Expected Behavior

The Cloud Agent starts on that issue. If GitHub is actually limited, the error should match my account quota. It does not.

Screenshots / Screen Recordings

Screenshot 2026-08-14 at 2.57.31 PM.png
Screenshot 2026-08-14 at 2.57.31 PM.png1084×498 53 KB

Operating System

MacOS

Version Information

Version: 3.15.19
VSCode Version: 1.128.0
Commit: de07bee81cefe43461ebf4f40c3d2d78d15052a0

For AI issues: which model did you use?

Not a model bug. Assign fails before a Cloud Agent starts.

For AI issues: add Request ID with privacy disabled

serverGenReqId_c0edbf76-df14-46af-8528-d5314869c33f
serverGenReqId_62801f3a-c901-42fc-92ef-6783d24915b2

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Where does the bug appear (feature/product)?

  • Cloud Agents and Automations
  • Grok Bot (launching a cloud agent from a Grok Bot chat)

Describe the Bug
From Grok Bot, launching a Cursor cloud agent fails with only this text:

Could not launch the cloud agent: GitHub is rate limiting requests. Please try again later.

That is the entire response. No HTTP status code, no headers, no JSON body. Listing cloud agents works (empty list). Launching one does not.

This is not the user’s own GitHub API rate limit. A personal GitHub token for the same account gets HTTP 200 from the GitHub API with about 4988 of 5000 remaining and can read the target private repo. GitHub status and Cursor status (including Cloud Agents) were All Systems Operational with no open incidents at the time.

GitHub was already reconnected in Cursor. Same error after reconnect.

Steps to Reproduce

  1. Connect GitHub in Cursor (including the private repo).
  2. In Grok Bot, ask it to launch a cloud agent on that private repo (for example to fix a failing CI test).
  3. Launch returns the rate-limit sentence above.
  4. Retry launch multiple times over 30-plus minutes. Same error.
  5. Confirm cloud-agent list works.
  6. Confirm the GitHub API with a user PAT is HTTP 200 and not exhausted.
  7. Confirm both status pages are green.

Expected Behavior
Grok Bot starts a cloud agent on the connected repo and returns an agent id or URL. If GitHub is actually rate-limiting, the error should include the HTTP status, rate-limit headers, and which credential or app was limited (user PAT vs Cursor GitHub App).

Screenshots / Screen Recordings
None. The launch payload is only that one sentence.

Operating System
(please fill: Windows / Mac / Linux)

Version Information
(please fill from Cursor, About Cursor, Copy)

For AI issues: which model did you use?
Grok Bot (default). No cloud agent was created, so there is no bc- id.

For AI issues: add Request ID with privacy disabled
I do not have a Request ID for the failed launches. No background agent id exists because launch never succeeded.

Additional Information
This started after Cursor’s Aug 17 incident “GitHub degradation affecting some Cursor services — Automations, Cloud Agents, Codebase,” which was marked resolved at 20:40 UTC. Launches still failed hours later. Grok Bot cannot file product feedback from this chat (privacy mode).

Status pages:

Does this stop you from using Cursor?
No - Cursor works, but with this issue. Grok Bot cannot start cloud agents, so it cannot ship repo fixes that way.

6

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Editor, Tab & Chat (autocomplete, Composer, in-editor agent)
  • Terminal & commands
  • Models, pricing & API keys (availability, Auto/Max, BYOK/Bedrock)
  • MCP & tools
  • Cloud Agents & Automations (cursor.com/agents, scheduled/event)
  • BugBot & Code Review
  • Cursor CLI
  • Cursor Mobile
  • Remote (SSH / Dev Containers / WSL)
  • Account, billing & login
  • Something else…

Describe the Bug
A clear and concise description of what the bug is.

Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. …
  2. …
  3. …

Expected Behavior
What is meant to happen here that isn’t working correctly?

Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)

Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)

For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…

Additional Information
Add any other context about the problem here.

Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

10

Update after more digging:

This does not look like my GitHub account being rate-limited.

Grok Bot can list cloud agents (empty list). Launch is what fails, with only: “GitHub is rate limiting requests. Please try again later.” No status code, no headers.

A personal GitHub token for the same account still gets HTTP 200 from the GitHub API with about 4988 of 5000 remaining, and it can read the private repo. So the user PAT is not exhausted.

Cursor’s Cloud Agents API documents a separate, very strict cap on listing GitHub repos through the Cursor GitHub App: 1 request per user per minute, and 30 per hour.
https://cursor.com/docs/cloud-agent/api/endpoints.md

Launch has to resolve the repo that way. List-agents does not. We also retried launch many times in one hour, which would trip that cap.

Cursor has also previously turned GitHub App / token-resolution misses into misleading errors (including treating transient GitHub conditions as a hard failure):

First error tonight was “Please reconnect GitHub.” After reconnect, every launch is the rate-limit sentence. That looks like the same family of bug: Cursor’s GitHub App path, mislabeled as GitHub rate limiting.

Happy to provide timestamps of the failed launches if useful. No bc- id exists because launch never succeeded.

11

Hey there!

Thanks for the report. We’re aware of some GitHub rate limiting issues (not specific to your configuration), and we’ve raised it to the team responsible! Will share updates here when we know more.

15

Same here! Please advise as soon as possible - this is a blocker for us

16

A few fixes are in the pipeline and will be deployed shortly to resolve the rate-limiting issue. We sincerely apologize for the disruption this has caused, and we’re grateful to everyone who took the time to report it.

18

Facing the same thing, just connected Slack Connect with Cursor:
Cursor [8:57 PM]

GitHub’s API rate limit was reached. Try again in a few minutes.
A simply Hi presented me this rate limit reached.