Re:Show HN: Amla Sandbox – WASM bash shell sandbox for AI ag...
by manojlds on Friday January 30, 2026 @04:12PM
(#46829975)
How does this all compare to using pyodide?
Re:Show HN: Amla Sandbox – WASM bash shell sandbox for AI ag...
by simonw on Friday January 30, 2026 @05:49PM
(#46831043)
A lot of it IS using Pyodide, but wrapping it in a way that's convenient to use not-in-a-browser.
Re:Show HN: Amla Sandbox – WASM bash shell sandbox for AI ag...
by sd2k on Friday January 30, 2026 @07:04PM
(#46831721)
I'm not super familiar with how pyodide works but I think it uses CPython compiled with Emscripten then needs to be run from a Javascript environment, and uses the browser's (or Node's) Wasm engine.
This uses CPython compiled to WASI and can (in theory) be run from any WASI-compatible Wasm runtime, in this case wasmtime, which has bindings in lots of languages. WASI uses capability based security rather than browser sandboxing and lets the host intercept any syscalls which is pretty cool. Wasmtime also lets you do things like epoch-based interruption, 'gas' for limiting instruction count, memory limits, and a bunch of other things that give you tons of control over the sandbox.
Pyodide/Emscripten might offer something similar but I'm not sure!
Re:Show HN: Amla Sandbox – WASM bash shell sandbox for AI ag...
by manojlds on Saturday January 31, 2026 @02:21PM
(#46839842)
Thanks for the explanation, need to dive in deeper into wasm / wasi - I didn't realize there was a difference.
Re:Show HN: Amla Sandbox – WASM bash shell sandbox for AI ag...
by simonw on Friday January 30, 2026 @02:38PM
(#46828873)
It looks like there's not mechanism yet in the Python bindings for exposing callback functions to the sandboxed code - it exists in the Rust library and Python has a ExecuteRusult.callback_invocations counter so presumably this is coming soon?
Any chance you could add SQLite?
Filed a feature request here: https://github.com/eryx-org/eryx/issues/28