← Back to digest
Tools & Demos

Cursor's cloud agents on your own infrastructure

What's this about?

Cursor's cloud agents can now execute on infrastructure you control — auto-scaling machine pools, or sandbox providers like AWS Lambda, Cloudflare, E2B, Modal and Vercel — while Cursor keeps running the agent loop.

What exactly is the split?

The brain stays with Cursor (planning, model calls); the hands move to you (code execution, file access). Enterprises get agents that never ship proprietary code to a vendor's compute, and the sandbox providers get an anchor customer for an emerging market.

Why is this worth noting?

"Bring your own execution environment" is becoming table stakes for enterprise agent adoption — and the roster of five sandbox vendors in one announcement shows agent-sandboxing is now an industry layer of its own.

← `ant apply`: infrastructure-as-code for agentsThe design thinking behind Grok Bot →