How I Learned to Stop Worrying and Love the Sandbox — Matt Brockman, E2B
- Source
- youtube.com
- Author
- AI Engineer
- Date
Context
sandboxes are isolated computers that need ordinary housekeeping, and an E2B workshop by Matt Brockman teaches that through deliberately broken environments. Per the description, participants find a process using nearly all of a 's CPU, memory pressure, and a file filling the disk, and each challenge runs in its own sandbox so a mistake can be reset.
The more transferable point is about running many of them. E2B templates preserve a running system's memory and filesystem so work can resume where it stopped, but Brockman discusses the tradeoff that forgotten processes also come back. Exercises on idle timeouts, so unused sandboxes stop consuming capacity, and on mapping each user to a fixed sandbox ID instead of round robin assignment, show what changes when a few sandboxes become hundreds. The recurring task, in the description's words, is keeping track of what runs where, what it can access and when to clean it up.
- Matt Brockman's E2B workshop teaches sandbox operations as capture the flag: kill a runaway process at 99.7% CPU, find memory pressure, and locate a file filling the disk, each in its own resettable environment.
- E2B templates preserve a running system's memory and filesystem state, so work can resume where it stopped.
- At fleet scale, the exercises let a task finish before shortening the idle timeout, and swap round robin assignment for a user-to-sandbox-ID map so each person returns to the same workspace.
- A cache exercise separates a template's readable files from the location that should receive runtime writes, part of tracking what runs where, what it can access, and when to clean it up.
Checking sign-in…
Loading comments…






