Running tasks in the cursor cloud can result in GitHub being banned

Every time I create a new GitHub account and associate it with a cursor, and then use the cursor’s cloud to run code, sometimes my GitHub account is inexplicably blocked, and four of them are blocked. Is there something wrong? I haven’t done anything that violates the rules. Why is this happening? Can you explain

Hey, thanks for the report. One important detail: the ban is happening on GitHub’s side, not Cursor’s. We don’t control their system, and we can’t remove or prevent the ban.

Most likely GitHub’s anti-spam or anti-abuse system is triggering. New accounts that immediately start automated activity and that’s what cloud agents look like to GitHub often get auto-flagged. Also, creating multiple new accounts for automation usually violates GitHub’s Terms of Service, so they may get banned one after another.

What you can do:

  • Use one main, established GitHub account with a normal history instead of creating a new one for each task.
  • If you think the ban is a mistake, appeal directly to GitHub Support: https://support.github.com/

On our side, sadly, we can’t influence this. GitHub makes the decision. Let me know if you have any other questions about how cloud agents work.