microsandbox

amazing! any point of comparison with microsandbox? [0] [0] https://github.com/superradcompany/microsandbox

what about msb? https://github.com/superradcompany/microsandbox

microsandbox is open-source and runs on linux, macos and windows: https://github.com/superradcompany/microsandbox/

it's been mentioned on this thread already, we think https://github.com/superradcompany/microsandbox/ is the closest OSS to it and we have a great DX and improving.

There's also microsandbox which has similar features: https://github.com/superradcompany/microsandbox (Not affiliated with them, just tried it out last week.)

Agreed. Network control and secret injection together with a microVM setup is as good as it gets right now, although I believe that we need more fine-grained tools down the road. It sounds like Microsandbox would be the perfect fit for what you are describing. I also built my own coding agent workbench on top of it (https://github.com/isolade/isolade). Microsandbox is quite cool, check it out: https://github.com/superradcompany/microsandbox

BETA: I have been following https://github.com/superradcompany/microsandbox a bit, very simple to get started with at least.

I can recommend microsandbox. More mature than smolmachines. I have tried both. https://github.com/superradcompany/microsandbox

I'm currently using herde[1] to handle/supervise multiple agents (with some patches I need to try to upstream) along with Nono[2] for sandboxing. This sandboxing approach avoids use of a microVM, which lets me use tooling I already have installed inside the sandbox. The downside is getting all the policies correct as it seems every project needs some new type of access, though Nono does try to make policy writing easy. I've been considering switching my approach to using a microVM through microsandbox[3]. The pro of this approach is you can essentially skip the policies and rely on the security of the VM boundary. The negative is that now you've lost all your installed tools, so you need to either provision at runtime or build something (like an image) beforehand to match your dev environment. I still don't know which is less maintenance.

TIL about Monty. A number of people have tried to sandbox [python,] using python and user space; but ultimately they've all concluded that you can't sandbox python with python. Virtual Machines are a better workload isolation boundary than Containers are a better workload isolation boundary than bubblewrap and a WASM runtime. eWASM has costed opcodes; https://news.ycombinator.com/item?id=46825763 From "Show HN: CSL-Core – Formally Verified Neuro-Symbolic Safety Engine for AI" (2026) https://news.ycombinator.com/item?id=46963924 : > Should a (formally verified) policy engine run within the same WASM runtime, or should it be enforced by the WASM runtime, or by the VM or Container that the WASM runtime runs within? > "Show HN: Amla Sandbox – WASM bash shell sandbox for AI agents" (2026) https://news.ycombinator.com/item?id=46825026 re: eWASM

This is very neat tech, but I think you might want to wait until you actually have Windows covered before making claims like https://github.com/microsandbox/microsandbox/blob/main/MSB_V...

Right. You can skip the `with` context manager and call start and stop yourself. There is an example of that here: https://github.com/microsandbox/microsandbox/blob/0c13fc27ab...

Yes! With the `scope` property. https://github.com/microsandbox/microsandbox/blob/0c13fc27ab...

Looks neat. If I understand correctly, I can use it to spin up backends on the fly? You have an ambitious list of languages to support: https://github.com/microsandbox/microsandbox/tree/main/sdk edit: A fleshed out contributors guide to add support for a new language would help. https://github.com/microsandbox/microsandbox/blob/main/CONTR...