Wasmtime interop. Also, if anyone is interested in the concept of "Sandboxed Local Agents", I’d love to hear your thoughts." title="I’m building "Steam for AI Agents" using .NET 8, WinUI 3, and Wasmtime (WebAssembly Sandbox).">full image - Repost: I’m building "Steam for AI Agents" using .NET 8, WinUI 3, and Wasmtime (WebAssembly Sandbox). (from Reddit.com, I’m building "Steam for AI Agents" using .NET 8, WinUI 3, and Wasmtime (WebAssembly Sandbox).)
Mining:
Exchanges:
Donations:
Hi everyone,I’ve been working on a project called NEXUS OS. The concept is essentially "Steam for Labor"—a platform where you can download autonomous AI agents to do work on your computer, but without the security risk of running raw Python scripts or EXEs.The Tech Stack (The fun part):UI: WinUI 3 (Windows App SDK) using C# and Mica effects for that modern feel.Runtime: Instead of running agents natively, I'm using Wasmtime to run them inside a WebAssembly sandbox. This means the OS controls exactly what the agent can access (Files, Network, etc.).Store Backend: I wanted to keep it decentralized/cheap, so the "App Store" actually fetches data directly from a raw GitHub repository.Packaging: Agents are distributed as .nxp files (custom ZIPs containing nexus.json manifests and bytecode).Current Status:I just finished the Kernel logic. I can now load a Wasm module, and through the linker, the agent can call host functions like create_native_window to spawn WinUI dialogs from within the sandbox. I also built a Publisher CLI that automates zipping and pushing new agents to the GitHub repo.Why I'm posting:I’m looking for feedback on the architecture, specifically regarding the .NET -> Wasmtime interop. Also, if anyone is interested in the concept of "Sandboxed Local Agents", I’d love to hear your thoughts.
Social Media Icons