This is not a billing or refund question. I’m trying to understand Cursor’s device-identification behavior and whether it is documented anywhere.
I recently noticed that simply logging into GrokBot appears to affect Cursor’s “Too many computers” protection.
What surprised me is that I did not send any messages or start any Agent tasks through GrokBot. I only completed the login.
So I’d like to understand:
Does Cursor officially treat GrokBot as a separate computer/device?
If so, I think this behavior should be documented much more clearly.
Before logging in, there was no indication that GrokBot would count as another device, no warning that the login could affect the device limit, and no way to see how many devices Cursor currently recognizes.
This is particularly confusing for developers who regularly use multiple environments and integrations.
It would be helpful if Cursor could clarify:
What exactly counts as a “computer” or “device”?
Does GrokBot count as a separate device?
Does authentication alone count, even without actually using the Agent?
Are third-party clients treated the same way?
Is there any documentation explaining this behavior?
Is there a way to view or manage the devices currently recognized by Cursor?
I think this is an important product/documentation issue because users should know before logging into another client whether that login will be treated as an additional device.
Grok Bot signs in to your Cursor account as its own device, and the cloud workspace it connects to can register as a separate device as well, which also counts toward your total. So simply completing a login is enough for it to be counted.
Thanks for the feedback on the documentation and on making connected devices clearer! I’ll pass it along to the team.
However, my immediate concern is not the documentation issue — I need my account to be unblocked.
I was completely unaware that logging into GrokBot would count as one device and that its cloud workspace could count as another device. I did not intentionally exceed any device restriction, and I did not even use GrokBot beyond completing the login.
Because of this unexpected behavior, my Cursor account is now restricted and my active development work has been seriously disrupted.
I understand this is disruptive, but this protection is an anti-abuse measure that applies equally to all accounts. We aren’t able to override or lift it for individual accounts. Existing devices should age out soon (within a day), and access is restored automatically.
To stay under the limit after that, you’ll need to reduce the number of devices signing in to your account.