Cloud Agent reaches creation limit when there's none created

Support Bug Reports
1

Where does the bug appear (feature/product)?

Somewhere else…

Describe the Bug

Hi there - I’ve been experimenting with Cursor’s Cloud Agents for a while, trying with different configurations: Ubuntu snapshot and through a Dockerfile. The Dockerfile turned out to be my preferred option as it normalizes the environment setup with a light base image.

During my tests, I constantly created and removed environments from the cloud agents section in the web dashboard, in a way that I could finally get the correct Dockerfile configuration for the Cloud Agent. However, whenever I removed an environment, I couldn’t create another one in its place, as I received the message “You’ve reached the limit for your current plan. Upgrade to Ultra to run more Cloud Agents simultaneously.” The message is curious since I don’t have an active Cloud Agent for any of my repos, but it says that I hit the limit.

As far as I understand, I can have one active Cloud Agent for a given repository, but it looks like I can’t create another one after deleting my current one. I also tried in another repository to check if it was bound to the first repo, but I got the same limit message.

Also, weirdly enough, if I wait one day to try again, the Cloud Agent creation goes through, but it hits the limit again if I create one for another repo (probably a rate limiting of 1 agent creation/day?).

Is there anything I am missing?

Steps to Reproduce

  1. Create a Cloud Agent, doesn’t really matter the method or the repo
  2. Delete the Cloud Agent (either finishing it or not - most of the times I didn’t finish its configuration)
  3. Try to create a Cloud Agent again for the same repo - it should show the limit message

Expected Behavior

It should allow me to have at least one active Cloud Agent for a given repo

Operating System

Linux

Version Information

(the issue is in the web dashboard, but pasting anyway)

Version: 2.5.17
VSCode Version: 1.105.1
Commit: 7b98dcb824ea96c9c62362a5e80dbf0d1aae4770
Date: 2026-02-17T05:58:33.110Z
Build Type: Stable
Release Track: Default
Electron: 39.3.0
Chromium: 142.0.7444.265
Node.js: 22.21.1
V8: 14.2.231.22-electron.0
OS: Linux x64 6.1.159-1-MANJARO

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

4

Hey, thanks for the detailed report.

This is a bug on our side. When you delete an environment config (Dockerfile/snapshot) from the dashboard, the internal agent records don’t get archived and they still count toward the concurrent Cloud Agents limit (8 for Pro). So after a few create and delete cycles, the limit gets “filled” with phantom agents.

The reason you can create again the next day is that the old records eventually time out and stop counting.

As a workaround, go to https://cursor.com/agents and check if there are any old or stuck agents you can archive. That should free up slots.

Let me know if the workaround helped.

5

The workaround worked. I archived all my agents, and it unblocked the creation of new ones. Thanks!

6

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.