# Self-hosted machines

By Steven Van · 2026-09-02

Cursor supports \*\*self-hosted machines\*\*, which let you keep tool execution entirely in your own network.

[Cursor](<https://creatorstoolbox.com/tools/cursor>)'s cloud agents can now run on machines you host yourself, keeping your codebase, build outputs, and secrets inside your own network while the agent handles tool calls locally.

- **My Machines** connects a single laptop or VM to your account for personal workflows, while **team pools** are named queues of workers for a team or enterprise. Pools aren't tied to one repository, so any available worker can claim a request, and capacity grows or shrinks as workers connect or disconnect. Idle machines can hibernate and restore within a reconnect window instead of staying warm between prompts.

- Cloud agents can also run on infrastructure you already use, including AWS Lambda, Coder, Cloudflare, Daytona, Modal, Namespace, Vercel, and E2B.

- Self-hosted workers now support computer use on Linux and Mac: with the right desktop packages, an agent can click, type, take screenshots, and drive the browser, and you can watch its desktop or take control from within Cursor.

Read the [full changelog entry](<https://cursor.com/changelog/self-hosted-machines>) for setup details.

[![](<https://ptht05hbb1ssoooe.public.blob.vercel-storage.com/assets/blog/cursor-run-on-remote-machines-loBz4KzTHKq1RvZG4Ka07UpsCIDYwx.png>)](<https://cursor.com/changelog/self-hosted-machines>)

![Cursor](<https://cursor.com/marketing-static/icon-192x192-light.png>)

Cursor

AI code editor built on VS Code — agents that edit across your codebase, run in the cloud, review pull requests, and now host your repos.

[View Cursor →](<https://creatorstoolbox.com/tools/cursor>)

[Original source](<https://cursor.com/changelog/self-hosted-machines>)

[Read Self-hosted machines on Creators Toolbox](<https://creatorstoolbox.com/blog/cursor-self-hosted-machines>)

---
Canonical source: https://creatorstoolbox.com/blog/cursor-self-hosted-machines