Feature request: launch Cloud Agents on a self-hosted worker without a git repo (via API/CLI)

Describe the request

We run Cursor’s self-hosted worker (agent worker start) on a Windows machine to work on a very large Perforce workspace (~1 TB). Git isn’t an option for us: the repo is too big and our data policy doesn’t allow mirroring it to git or Origin.

The web UI already handles this well. On cursor.com/agents I can pick my worker and start a new chat with no repository, and the agent works directly in the Perforce workspace. That runs fine.

The problem is automation. The public API (POST /v1/agents with env: {type: "machine", name: "<worker>"}) rejects repo-less requests with:

Repo-less private-worker requests require a valid workspace binding, one specific worker name, shared-assignment metadata, and an owner filter matching the authenticated user.

These fields aren’t documented, and the CLI has no way to start a repo-less agent on a specific worker either. As a result, the only way to start new agents from scripts or other automation is to drive the web UI with browser automation, which is fragile.

Request:

  1. Support repo-less launches to a named self-hosted worker in the public API, the same way the web UI does, or document the fields the error asks for.
  2. Optionally, add a CLI command for the same thing, e.g. agent launch --worker <name> --prompt "...".

This would make self-hosted workers usable for non-git VCS like Perforce, which is common in game development.

Hey @WEIKANG_RUAN, sorry for the slow reply, and thanks for the clear write-up.

Right now, starting an agent on a named self-hosted worker without a repo only works from cursor.com/agents. The public API’s machine target only accepts a worker name, and the fields in that error aren’t something the API lets you send, so there’s nothing to add to your request today. The CLI doesn’t have a command for this either.

We’ve passed this along as a feature request. We’ll post any updates here!

Thanks for the update, kevinn — much appreciated. I’ll keep an eye on this thread for further progress.