BusDK Update
Persistent disks in the browser, and a first package manager for Bus Engine OS
Two early pieces make the browser-hosted Bus Engine OS feel more operable: an optional persistent-disk path for browser VMs, and bus-pkg, a first package-database and package-manager surface for the system.
The throughline is state. A browser-hosted, AI-agent-operated OS needs a way for files, package choices, and configuration to carry forward across sessions while the package layer gives agents a vocabulary for changing the system deliberately.
July 1, 2026Bus Engine OSpersistent browser disksbus-pkg
A browser VM is useful for demos as soon as it boots. It starts becoming operable when it can remember what changed. The new persistent-disk option is a step in that direction for the browser-hosted Bus Engine OS profiles: state can be attached to the VM through browser storage, with OPFS as the browser-side storage target.
This remains early. The right framing is optional persistent state for experiments, development flows, and agent-operated sessions where losing every filesystem change after a reload would limit what the OS can do. Durability behavior, browser quotas, cleanup controls, and user expectations still need careful product treatment before this should be treated as a stable storage contract.
The second step is bus-pkg. Its first package-manager path connects Bus Engine OS to a package database, installs named packages from a package repository, and proves package operations through the dispatcher. That is enough to make packages part of the operating surface instead of only build-time image contents.
Together, these changes point at the same product shape: a browser-hosted OS that an AI agent can operate across turns. Persistent disks give the session somewhere to keep state. bus-pkg gives the OS a package vocabulary for adding capabilities inside that state. The current implementation is still experimental, but it moves the work beyond a one-boot artifact toward an environment that can be changed, inspected, and resumed.
As the surface settles, docs.busdk.com is where browser-VM storage expectations, profile behavior, and the supported bus-pkg command surface will be tracked.
