BusDK Update

Bus Engine OS boots in your browser

Bus Engine OS now has an experimental browser-hosted path: WASM-hosted QEMU boots a RISC-V system and draws a framebuffer console inside a browser tab.

Think of it as Docker Desktop for the browser. Docker Desktop runs a hidden Linux VM so Windows and macOS apps can reach Linux-only capabilities through APIs. Bus Engine OS is working toward the same for browser and frontend apps: Linux-only services behind APIs that a browser experience can call.

July 6, 2026Bus Engine OSQEMU/WASMRISC-V framebuffer

Summary

TL;DR

A zero-install evaluation flow can boot an experimental RISC-V Bus Engine OS image in a browser tab and show the framebuffer console.
The capability points at a Linux service layer for browser apps: agentic AI backends such as the Codex App Server, containers, backend logic for static sites, and self-compiling static sites are the kinds of Linux-backed capabilities this path aims to expose through APIs as it matures.
This is early proof-of-capability work. Treat it as an evaluation path, then use docs.busdk.com as the next stop for module docs and operating notes.

The browser path is less about a novelty terminal and more about where the Linux boundary can live. QEMU runs through WASM, the guest is RISC-V, and the visible proof is a framebuffer console you can watch progress in the tab. That is enough to evaluate the boot path without installing a local VM, container runtime, or desktop package.

The Docker Desktop analogy is deliberate. Desktop keeps Linux in a VM and surfaces Linux-only capabilities to a host that cannot run them directly. Bus Engine OS brings the same model to browser apps: keep the Linux side behind APIs, and let the frontend evaluate, orchestrate, and eventually depend on those capabilities without a native install step.

For agentic AI, that means a browser app can have a path toward Linux-backed service capabilities such as the Codex App Server. The same shape can support containers, backend logic for static sites, and static sites that compile themselves from inside the browser-hosted environment. The current browser-hosted flow is experimental, so the useful framing is zero-install evaluation and proof of capability rather than a finished production platform.

The practical next step is intentionally soft: follow the Bus Engine OS documentation at docs.busdk.com as the browser-hosted path opens up for broader evaluation.