Cursor Self Hosted Agents and Team Plan / Worker Pool

Support Help
, ,
1

Hi,
currently at Team plan and interested trying out recently released self-hosted agents.
It is not clear from the docs and the agent cli help on how we can register an agent as a team shared worker pool.
Running a self-hosted agent with either the browser login method or a personal API key, registers it as a personal worker.
Service account API keys are available to enterprise plan afais

6

Hi @Team, Thanks for the report. This has been fixed, and you should see it reflected soon in an upcoming regular release.

Thanks!

Kevin

9

@kevinn should users on the team plan be allowed to use self-hosted agents? Right now the feature required Service Account API keys, which are only available on Enterprise.

10

Is there any movement on this? we’re on teams and we’d like to use pools, as well.

11

Hi all, @here

I do have an update on this. Teams can use self-hosted agents. However, self-hosted pools require a service account API key, which is currently enterprise only. Will keep you updated on any movement here.

13

Will service account API token be available on Team plans shortly or never?

14

Hi, in your documentation you mentioned the prereq of self hosted pool is a team plan, but in this thread it seems like it is only available in enterprise.

image
image1130×1576 167 KB

17

I don’t have a timeline at this time unfortunately however we have this thread linked internally so we can alert you when there’s movement on this front.

18

Sorry, Charlie, this is currently a misstatement in our Docs. Enterprise is required at this time.

20

So pool workers only for enterprise?

21

Hi @lasc — yes, that’s correct as of today.

Teams can run self-hosted Cloud Agents, but only as personal workers (under “My Machines”). Self-hosted pools — the centrally managed, shared worker fleets — currently require a service account API key, and those are only available on the Enterprise plan.

We’ve since corrected the docs to reflect this: the Self-Hosted Pool page ( Self-Hosted Pool | Cursor Docs ) now lists a Cursor Enterprise plan and a service account API key as prerequisites.

22

Cloud agent cant use local mcp, local gitlabs. personal machines not visible across the team.
self-hosted-pool still showing in dashboard and telling “No team-scoped workers are connected. Connect a team worker or ask a team admin to set one up.”

If this could be enabled for a team would be great, as personal workers are useless for a TEAM on a TEAM plan :wink: