51–55 of 55 posts
The WASM sandbox per agent with typed ABI is a really clean isolation model. Most agent runtimes I've seen just throw everything into one process and hope for the best. Curious about the IPC layer between agents. When agents communicate with each other, is there any access control on what one agent can request from another? Or is it open by default? In practice the moment you have multiple agents that persist and tal…
> Currently it runs as a desktop app on Linux, macOS, and Windows Does that mean it's not actually an OS?
Hey. This is a fair remark and logical too. It's build to run in a sandbox on other OS now to ease uptake. Asking people to install a new OS because "trust me bro" is not gonna work. That said it is build as an os. It generates real wasm that runs directly on the machine. Porting to baremetal is next on the backlog. It will require embedding rust cranelift directory into pneuma amongst other things but the hardest/bi…
Well, it's not directly on the machine. You still need the wasm engine/runtime to run it
With traditional software you at least have a binary you can inspect. Here the "program" is a generated Rust module that may never exist again in the same form. That's a genuinely hard problem for any use case where you need to reproduce or explain behavior after the fact.
The community agent store helps for sharing, but it also raises the question: when a downloaded agent does something wrong, who's responsible and how do you trace it? This feels like the unsexy infrastructure problem that'll define whether Pneuma can be trusted for anything beyond personal use.