Cursor lets Cloud Agents run on your own self-hosted machines
Tool execution stays inside your network — AWS Lambda, Modal, E2B and more — plus a Vercel Sandbox path, so locked-down teams can finally run agents.
Copy markdown
Tool execution never leaves your network
Cursor's Sept 2 update lets Cloud Agents run on self-hosted machines, so your code and secrets stay on infrastructure you control instead of Cursor's cloud. Computer-use runs on Linux and Mac.
Dynamic pools across eight backends
Machines schedule on demand — a personal 'My Machines' plus scalable 'Team pools' — with adapters for AWS Lambda, Modal, E2B, Cloudflare, Daytona, Namespace, Coder and Vercel. Point agents at compute you already pay for.
The unlock for locked-down teams
This is what compliance-blocked shops were waiting for: regulated teams can adopt background agents without code or credentials touching a third-party cloud. Same Cursor planning and orchestration, your hardware.
A managed path via Vercel Sandbox
The day after, Vercel added running Cursor Cloud Agents inside Vercel Sandbox: isolated micro-VMs with scale-to-zero workers and durable orchestration — if you'd rather not wire up your own pool.
Elsewhere: GPT-6 Astra gets a Pro tier
OpenAI's Astra now has a 'Pro' setting live on OpenRouter — the same model with reasoning.mode=pro, $10/$50 per million tokens and a 1M-token context. Flip it on for the hardest agentic runs.