I’m trying to set up a machine of mine with cursor and a self-hosted agent that my other instances can all make calls through so I have a central source of truth for everything on one machine. I don’t see how to accomplish this. I’ve got an Ultra plan.
Hi @NorseGaud Certainly!
You want My Machines, which is called Remote Control in some parts of Cursor. With an individual Ultra account, use a personal worker rather than the team-oriented Self-Hosted Pool.
Set up the central machine
Install the Cursor CLI:
# macOS, Linux, or WSL
curl https://cursor.com/install -fsS | bash
Sign in with the same Cursor account used on your other devices:
agent login
Open a terminal in the repository you want the machine to serve, then start the worker:
agent worker start --name "central-machine"
The name is optional, but it makes the machine easier to recognize. Keep this process running while you want the machine available.
Use it from another device
- Sign in to the same Cursor account.
- Open the Agents view or cursor.com/agents.
- Open the Run on or environment picker.
- Select
central-machineunder My Machines or Remote Control. - Start the agent normally.
The agent’s terminal commands, edits, browser actions, and local command-based MCP servers will execute on the central machine. The agent loop still runs in Cursor’s cloud, so this does not route every model or API request through your machine.
A worker is associated with your user and repository. To serve multiple repositories, open each repository checkout and start a separate worker process. Git should remain the source of truth when coordinating changes between devices.
No inbound ports are required. If the machine does not appear, run this from the repository directory:
agent worker start --debug
Also confirm that the worker is still running, both devices use the same Cursor account, and the checkout has the expected Git remote.
For the complete setup, authentication, networking, and troubleshooting steps, see Cursor’s My Machines setup guide.
Let me know if you have any follow-up questions!
Thanks! Are Automations not able to target this machine?
For an individual Ultra account, Automations cannot target a personal My Machines / Remote Control worker. Enterprise customers can do this using an enterprise Self-Hosted Pool.
However, you can set up regular automations that use Cursor Cloud agents here: https://cursor.com/automations
Ah darn 
This is why I needed it Can individuals pay for a plan that supports this without going full Enterprise?
Hi @NorseGaud Not today. Automations on a self-hosted worker need an Enterprise Self-Hosted Pool. There isn’t an individual plan for that.
You can still run Automations on Cursor Cloud: https://cursor.com/automations, and you can still send interactive work to that machine from Slack, GitHub, or Linear. Details: My Machines | Cursor Docs