Sandbox: Run untrusted AI code safely, fast
1–10 of 32 posts
Re: Sandbox: Run untrusted AI code safely, fast
#21. coderunner - https://github.com/instavm/coderunner
Re: Sandbox: Run untrusted AI code safely, fast
#3Re: Sandbox: Run untrusted AI code safely, fast
#4Re: Sandbox: Run untrusted AI code safely, fast
#5Re: Sandbox: Run untrusted AI code safely, fast
#6If you don't want to depend on cloud, have a mac, then you can run a sandbox locally on you mac. I have built an apple container (not docker) based sandbox to run arbitrary code - coderunner[1]. It is quite fast. And apple container provides one vm per container unlike docker on macos which shares the vm across all containers. Coderunner is good for processing sensitive docs locally in a secure sandbox. 1. coderunner…
Also if it is agentic, why is it less cloud based than eg Claude code? Are there LLMs running locally?
Re: Sandbox: Run untrusted AI code safely, fast
#7Re: Sandbox: Run untrusted AI code safely, fast
#8Re: Sandbox: Run untrusted AI code safely, fast
#9I had a brief glance at running firecracker VM's locally as that sounded interesting, but it doesn't seem too easy.
Does anyone know of any good solution that improve the UX of that (running some firecracker VM's locally)?
Re: Sandbox: Run untrusted AI code safely, fast
#10This seemed quite interesting but it seems to run them on GCP rather than locally. I had a brief glance at running firecracker VM's locally as that sounded interesting, but it doesn't seem too easy. Does anyone know of any good solution that improve the UX of that (running some firecracker VM's locally)?
It uses KVM directly on Linux and Virtualization.framework on macOS, with a builder API for VM configuration. For AI sandboxing specifically, it has a higher-level "sandbox" mode with a guest agent for structured command execution and file I/O over vsock. You get proper exit codes and stdout/stderr without console scraping.
Also supports pre-warmed VM pools for fast startup and shared directories via virtio-fs.
I'm planning to support OCI images, but not sure if that's important to people. I typically just build my own root disks with Nix.