Are we defaulting to VM-level sandboxing before understanding the threat model? 3 samhita-alla 5 months ago 3 comments
What it took to make a multi-agent trading simulation durable and observable u union.ai 1 samhita-alla 1 year ago 0 comments
How I dubbed a 16-second video with lip sync for $0.50 using open-source models u union.ai 15 samhita-alla 2 years ago 0 comments
Plane One: Pay once, use forever project management tool p plane.so 1 samhita-alla 2 years ago 0 comments
Want to get started with LLMs? Here's what you need to know f flyte.org 145 samhita-alla 3 years ago 25 comments
For example, what about a sandbox that isolates arbitrary user code in its own process using kernel-level primitives like user namespaces, Landlock and seccomp? That's the same class of problem Claude Code and Codex are solving when they execute model-generated commands, and it should also limit filesystem and network access as you mentioned. It's process-level isolation rather than VM-level isolation, but it still provides meaningful containment. What do you think?
My concern is that people often default to VM-level isolation without really thinking through what it's meant to protect against and whether they actually need it. It comes with a fairly heavy infra burden and isn't necessarily the right answer for every use case.