Run Cursor Cloud Agents on Prized
Updated
Run the commands and edits of Cursor Cloud Agents on your box through Cursor's My Machines: start a Cursor worker in your project, then pick the box at cursor.com/agents, in Slack or GitHub, or in Cursor's API.
On this page7
Cursor runs the agent; with My Machines, its terminal commands, file edits and git run on your box, in your project, with your tools. The box connects out to Cursor, so nothing connects in.
Before you start
- A Cursor plan with Cloud Agents. My Machines needs no Enterprise plan. On a team plan, an admin turns on Allow Self-Hosted Machines in Cursor's Cloud Agents dashboard.
- Cursor's GitHub integration with access to the repository, set in Cursor's dashboard. Cursor checks it even when the agent runs on your box.
- A box. Sign up at prized.dev: the tour starts one on $30 of free credit with no card (Quickstart).
1. Put your project on the box
In your project folder, a checkout with its GitHub remote:
prized setup . --sync --agent cursor --install-cursor --no-startIt syncs the folder, .git included, with ~/code/myproject on the box (Sync) and installs the Cursor CLI there. Cursor sends an agent to the box whose checkout has the agent's repository as its remote.
2. Sign in on the box
prized sshOn the box:
NO_OPEN_BROWSER=1 agent loginOpen the link it prints in a browser on any device and approve it. Once per box is enough.
3. Start the worker
Back on your machine:
prized exec --detach --keep-awake --cwd code/myproject -- '~/.local/bin/agent worker start --name myproject-box'The worker connects the box to Cursor as myproject-box and runs until you stop it. --keep-awake keeps the box from auto-pausing under it, so the box stays up, and is billed as awake, until then (Detached processes). prized exec --ps shows the worker, and prized exec --kill with its id stops it.
4. Run an agent
At cursor.com/agents, open the menu that sets where the agent runs, choose myproject-box under My Machines, and send the task. From Slack or GitHub, add worker=myproject-box to the request: @Cursor worker=myproject-box fix the flaky test.
From a script, with a Cursor API key from Cursor's dashboard:
curl https://api.cursor.com/v1/agents -u "$CURSOR_API_KEY:" -H 'Content-Type: application/json' -d '{"prompt": {"text": "Fix the flaky test"}, "env": {"type": "machine", "name": "myproject-box"}, "repos": [{"url": "https://github.com/you/myproject"}]}'How it behaves
- In your checkout as it is. The agent edits the files on the box, on their current branch, and sync brings each edit to your laptop. Agents on the same box share the checkout.
- With the box's own credentials.
git pushandghuse what you set up on the box; Cursor's dashboard secrets don't reach it. - While the worker runs. If the box restarts, run step 3 again.
Troubleshooting
| Message | Fix |
|---|---|
Private workers are not enabled for this team | A team admin turns on Allow Self-Hosted Machines in Cursor's Cloud Agents dashboard |
The SCM integration does not have access to repository … | Give Cursor's GitHub integration access to that repository |
Authentication required for worker mode | Run step 2 |
worker=… is registered on your machine but for a different repository | Start the worker in a checkout of that repository |
| The box is missing from the picker | On the box, agent worker debug checks the sign-in, the repository and what Cursor sees |