Vasek Mlejnsky(@mlejva):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_ai 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:

2026.09.02 21:24

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_ai 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:

Cursor@cursor_ai

2026.09.02 21:07

You can now run Cursor cloud agents on your infrastructure, including pools of machines that automatically scale with demand. This lets you give agents access to internal services or specialized hardware, while the agent loop stays in Cursor.