Under the hood: your input goes to an LLM, which generates a self-contained Rust module. That gets compiled to WebAssembly in under a second, then JIT-compiled and executed in a sandboxed Wasmtime instance. Everything is GPU-rendered via wgpu (Vulkan/Metal/DX12). If compilation fails, the error is automatically fed back for correction. ~90% first-attempt success rate.
The architecture is a microkernel: agents run in isolated WASM sandboxes with a typed ABI for drawing, input, storage, and networking. An agent crash can't bring down the system. Agents can run side by side, persist to a local store, and be shared or downloaded from the community store.
Currently it runs as a desktop app on Linux, macOS, and Windows. The longer-term goal is to run on bare metal and support existing ARM64 binaries alongside generated agents. A full computing environment where AI-generated software and traditional applications coexist.
Built entirely in Rust.
I built this because I think the traditional software model of find an app, install it, learn it, configure it; is unnecessary friction. If a computer can generate exactly the tool you need in the moment you need it, and then keep it around when it's useful, why maintain a library of pre-built software at all?
Free tier available (no credit card). There's a video on the landing page showing it in action.
Interested in feedback on the concept, the UX, and whether this is something you'd actually use.
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/biggest and most architectural part is already done: wasm. You can check out the blog for more info.
I had a conversation with Claude on it. I work as an artist and webdev, so excuse my lack of technical knowledge on the matter: https://claude.ai/share/8b40cf7f-ecc6-452f-a550-3d1e5416b3e5
Building apps on the fly seems cool, But hits the frustration when they don't work at times, When building as a side project we tolerate it because we are in building phase, But when using we might not tolerate the issues.
Finally the security also plays a major role, So instead of building apps at runtime, We need agents and skills as portable objects.
For this to be practical you really need to build things iteratively and asking the user questions, rather than attempting at one shot half assed ideas
Also most people are better explaining details with voice rather than text.
Pneuma reminds me a little bit of Yansu AI, a project I saw recently on HN that proactively builds apps with AI (https://yansu.app/)
However, I'd never use it. Reason: having everything dynamically created JIT means there's a trade-off somewhere else; in this case, it's energy consumption. I'd rather "cache" applications (ie. have them as installable software, which has been built just once) than endlessly recreate software from scratch each time, with all the energy usage that entails.
Does that mean it's not actually an OS?