Cursor x E2B Many of our customers use E2B in their internal development workflows. Some work in regulated industries where code and internal services can’t leave the company. For teams that need control over the execution environment, Cursor’s cloud agents can now use E2B as their machine. With Self-Hosted... Machines, Cursor handles the agent loop while E2B runs the code. Teams can give agents bigger machines and start them from custom E2B templates, so their Cursor workloads boot straight into an environment with internal dependencies already in place. Try it:show more

I'll miss you old friend

will be remembered

@cursor_ai + @e2b 🤝

@cursor_ai a perfect match

🔥🔥🔥

🚀🚀🚀

custom E2B templates with internal dependencies already baked in is a pretty big unlock for regulated teams. how are you handling secrets and network access once the Cursor agent is running?

Possibly dumb question, but does this include VNC?

Yes. Cursor can do computer use with the sandbox

nice

agent loop in Cursor, sandbox on your metal — that's the regulated team setup

That’s huge! Congrats Vasek. Great integration

Thank you Marc!

"code and internal services can't leave the company" is the sentence that closes the deal in regulated shops. the split you describe, loop in one place and execution in another, is also what makes the audit conversation easy: you can point at exactly one box and say that's where it ran.

Self-hosted machines for regulated teams. Cloud agents were never the hard part — keeping code + deps inside the firewall was. This is the missing middle.

Running the sandbox inside the customer's network is the unlock, not the model. Most of the shops I talk to are not blocked on capability, they are blocked on the fact that the interesting data lives behind a VPN and a compliance owner who will never approve egress. Keeping the execution local and the loop remote is the right split.

受监管行业不用再在合规和效率之间二选一了

E2B integration opens up custom boot environments with dependencies already in place, we actually covered why that's such a big deal for development workflows:

agents reaching internal services is the part that turns into support load later. every extra surface I open comes back as someone asking why it behaved. pruning is the expensive half of shipping.