Skip to main content
Watch: I Built an AI App Without Leaving Databricks

Cursor error

Cursor: Private worker limit exceeded

Error message
Private worker limit exceeded

Status: By designLast verified 3 documented fixes2 sources

What it means

A Cloud Agent run on Self-Hosted Machines does not start because the team hit the connected worker cap.

Causes

  • The connected self-hosted worker cap was reached: 200 per user, 1000 per team.

How to fix it

  1. Fix 1.

    Disconnect unused workers, or contact sales to discuss higher limits.

  2. Fix 2.

    Check capacity in the Cloud Agents dashboard or call the summary API, which returns connected and in-use worker counts for your user and team.

    Terminal
    curl --request GET \
      --url "https://api.cursor.com/v0/private-workers/summary" \
      -u "$CURSOR_API_KEY:"
  3. Fix 3.

    Run the worker preflight report for auth, connectivity, routing and backend visibility.

    Snippet
    agent worker debug

More Cursor errors

All 18 Cursor errors

FAQ

What does "Private worker limit exceeded" mean in Cursor?

A Cloud Agent run on Self-Hosted Machines does not start because the team hit the connected worker cap.

How do I fix "Private worker limit exceeded"?

There are 3 documented fixes. Start with the first: Disconnect unused workers, or contact sales to discuss higher limits.

Is this Cursor error fixed?

Status: By design. Expected behavior, not a bug. The documented fixes change the setup that triggers it.

Sources

Last verified against 2 sources: official docs, maintainer replies and release notes.

Newsletter

Fixes for the tools you use, weekly

One email per week. New coding agent releases, what broke, and how developers are working around it.