Remote-agent workers each count as a separate device, exhausting the per-account device cap

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

My Windows workstation is currently blocked by the per-account device cap with the error “Too many computers used within the last 24 hours for the same Cursor account”. I use three physical machines: one Windows PC, plus two Linux servers that I reach through Remote-SSH and the remote agent. The account is not shared with anyone else.

On one of those servers, the remote agent keeps one worker per project directory, and each worker registers itself with its own name and label, for example:

cursor-agent worker start --worker-dir /home/xxx/project/foo --name “~/project/foo at myhost” --label name=cursor-agent-worker-xxxx

On that single host I counted 17 worker registrations, coming from 17 different project directories. Several had been running for hours, one for more than five.

If each of these workers is counted as a separate device, then the number of “computers” grows with the number of project directories I open, not with the number of machines I actually own. One Linux server can therefore use up a large number of device slots. For anyone whose job involves many servers and many checkouts, the cap is reached without any account sharing at all, and the penalty is a 24-hour block of the desktop client.

I have already stopped the stale workers and I am keeping the setup to the three machines I really use.

Steps to Reproduce

  1. Use one account on a Windows desktop, plus one Linux server reached through Remote-SSH / the remote agent.
  2. On the server, open the agent in several project directories (5 to 10 is enough), so that a worker process is started for each one.
  3. Let the workers keep running for a while, then close the sessions without stopping the processes.
  4. Start the desktop client on the Windows machine.
  5. The client is refused with “Too many computers used within the last 24 hours for the same Cursor account”, and it keeps failing for the rest of the 24-hour window.

Expected Behavior

Workers started on the same host should collapse into a single device identity, keyed on the machine rather than on the workspace path, so that only real computers count against the device limit. Opening a workspace in a new project directory on the same server should not use up another device slot.

Operating System

MacOS

Version Information

Cursor desktop app on Windows 11 (current stable build), with the remote agent on two Linux servers (Ubuntu 22.04 and Rocky 9). The worker processes are the ones shipped with the desktop app, so their version matches the desktop build.

Additional Information

The account-specific request (device record reset) has already been sent to [email protected] as the forum bot advised. This thread is only about the worker counting behaviour, so no account details are included here. I am happy to provide logs or the worker list if it helps.

Does this stop you from using Cursor

Yes - Cursor is unusable

Hi, thanks for the detailed write-up and for stopping the stale workers.

We looked into this, and the agent workers weren’t what pushed you over the limit. Every worker on a host reports the same machine identity, taken from the operating system. The worker directory, --name and --label play no part in it, so your 17 workers on one server counted as a single computer. None of the devices recorded against your account in this window came from the CLI or from remote agent workers.

Everything we see comes from the Cursor desktop app, and it doesn’t look like a single Windows PC. There are several distinct Windows installations, each running different app versions, some active at the same time, with new ones appearing over the course of the day.

This can be caused by a pooled or non-persistent virtual desktop, a Cursor profile that’s synced or copied between machines, or the desktop app running on your Linux servers through remote desktop or X forwarding. It can also mean someone else is signed in to your account. Each Cursor account is meant for one person, so signing out everywhere and changing your password makes sure only your own machines remain.