Loading video...
Video Failed to Load
Today's sandbox protects the agent. Tomorrow's may need to protect the code it writes. Oleg Šelajev 🇪🇪🧊🐳 talks with Docker Sandboxes PM Eric Jia about where sandboxing is headed and what developers should be preparing for next.
12,161 views • 3 months ago •via X (Twitter)
2 Comments

Jason Fleagle3 months ago
@shelajev Protecting generated code means treating output as an untrusted artifact. Build it without ambient credentials, scan dependencies and secrets, run tests in a disposable environment, compare declared versus observed behavior, and require a signed acceptance step before merge.

RH Fardin3 months ago
@shelajev Protecting the agent isn't enough if its output can quietly poison the codebase. Sandboxing generated code will become table stakes.

















