Cloud Agents API: support Origin repositories (all Origin URL forms rejected with repository_access)

Ideas Feature Requests
, ,
1

Feature request for product/service

Cloud Agent (GitHub, Slack, Linear,…)

Describe the request

Request: let the public Cloud Agents API (POST /v1/agents) target Cursor Origin repositories — at least for self-hosted “My Machines” workers.

Setup (reproducible today)

  • Team is on the Origin early beta. Test repo is Origin-only (never linked/mirrored to GitHub): https://origin.cursor.com/<team>/<repo>.git
  • Cloned it locally and started a worker inside the clone: agent worker start --name my-worker
  • The worker registers fine and shows up in GET /v0/private-workers with repo: https://origin.cursor.com/<team>/<repo> — so the worker side already understands Origin remotes.

Problem

POST /v1/agents with env: {"type":"machine","name":"my-worker"} rejects every Origin URL form:

repos[0].url Error
https://origin.cursor.com/<team>/<repo>.git (also tried without .git, without scheme, /git/… path, short <team>/<repo>) repository_access: You do not have access to repository …, or the repository does not exist.
https://cursor.com/codebase/<team>/<repo> validation_error: Failed to determine repository default branch (adding startingRef: "main" → [invalid_argument])

Omitting repos entirely returns:

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.

…but the public schema rejects any extra keys (Unrecognized key(s)), so that flow doesn’t appear to be reachable from the public API.

The exact same worker + API flow finishes successfully (FINISHED) when the anchor repo is on GitHub — so this is specifically the API’s repository check not recognizing Origin, mirrored or not.

Why it matters

We launch agents on self-hosted My Machines workers through the Cloud Agents API and would like to host the repo on Origin instead of GitHub — but today Origin repos can’t be targeted via /v1/agents at all.

Either of these would unblock us:

  1. /v1/agents accepting origin.cursor.com repo URLs (with access checked against the team’s Origin permissions), or
  2. exposing the repo-less “use the worker’s registered repo” flow in the public API schema.
6

Hey @weg-selim, thanks for the detailed write-up!

This is a known gap and the team is actively working on Origin support for Cloud Agents, including the API path you’re using. Origin repos already work for cloud agents started from the dashboard, and API support is on the way.

8

Thanks Colin, great to hear it’s actively being worked on!

Would you be able to share a rough ETA for the API path — even a ballpark range (e.g., a couple of weeks vs. a month or two)? No need for a firm commitment; we’re just deciding whether to wait for Origin or keep our GitHub-based flow in the meantime, so any rough timeframe would really help us plan.

Also, if there’s an early beta / preview program for this, we’d be happy to try it out ahead of time and share feedback.

Thanks again!

9

I don’t have an ETA to share, but I expect sooner than later. We are very excited to have folks using Origin. :slight_smile: