Summary: Haiku released R1/beta6 on August 26, 2026, nearly two years after R1/beta5 and about a week after the project’s 25th anniversary. The release resolves more than 530 bug and enhancement tickets, adds official Firefox-based browsers and experimental NVMM acceleration, and states that first-party components contain no AI-generated code. Performance work cut cold and hot git status times and nearly halved a HaikuWebKit rebuild, while ARM64 desktop booting and multiprocess WebKit remained unshipped.
Haiku’s R1/beta6 shipped on August 26, 2026 — close to two years after the preceding beta, R1/beta5, which landed in September 2024, and roughly one week on from the project’s 25th anniversary. Haiku is the open-source desktop operating system that re-creates BeOS, maintained by a small team made up mostly of volunteers, and the release notes page says outright that no code or other materials generated by “AI” appear in first-party components. This release folds in almost two years of the development team’s work, resolves more than 530 bug and enhancement tickets, and is described as the project’s most polished and stable release so far.
What This Release Brings
Two things draw the most attention. The first is browsers: once beta5 was out, browsers built on the Firefox codebase started appearing in the software depots — buggy at first, and carrying no official branding. Over the following two years the ports settled down, and Mozilla recently granted permission to use the official “Firefox” name. HaikuDepot now also stocks LibreWolf, Waterfox, Floorp and Icedove, a de-branded Thunderbird, with x86_64 the only architecture for the moment. The second is virtualization: Haiku has taken on NVMM, the NetBSD virtual machine monitor, which gives QEMU hardware acceleration on x86_64 hosts equipped with Intel VT-x or AMD-V and covers 32- and 64-bit guests along with SMP, though it is still marked experimental. There is a port of the Go compiler and runtime (version 1.26.1) in the repositories as well — enough, in fact, to build Hugo, the static site generator that produces Haiku’s own website. Past those headlines, the notes credit hundreds of smaller fixes touching “practically every area of the system,” with the project’s monthly activity reports holding the full accounting.
Performance: git status and Full Builds
System-wide optimization runs through the entire release: MIME sniffing is 5–10x faster; pipe throughput climbed from hundreds of MB/s into the multiple GB/s range; kernel locking granularity, malloc size classes (untouched since 2007) and the directory-entry cache were all reworked. Real workloads make the payoff visible. On a repository holding more than 160,000 files, git status fell from roughly 33 seconds to 20 seconds with a cold disk cache, and from 15 seconds to 2.5 seconds with a hot one. A full rebuild of HaikuWebKit on the same buildhost took 4 hours 53 minutes under beta5 and 2 hours 33 minutes under beta6 — close to half. Memory management saw an overhaul too: a new userland allocator built on OpenBSD’s implementation plus a global caching layer, and 32-bit systems can once again boot with as little as 128 MB of RAM. The list continues — basic library calls such as memmove and strcmp were rewritten, pre-mapping heuristics for large executables speed up compilers such as gcc, and kernel malloc size classes were retuned for the first time since 2007.
Desktop Experience Catches Up
app_server — Haiku’s display server, window manager and drawing server — can now come back from a crash with every running application reconnecting and re-establishing its state, and no reboot is required. The screenshot tool gained area selection; the team monitor groups child processes beneath their GUI parents; Tracker supports folder-filtering queries over the filesystem’s indexed attributes; SoftwareUpdater clears out old “previous states” on its own. Hardware compatibility improved substantially for machines built in the last five years, additional USB ethernet and Wi-Fi adapters work through the FreeBSD/OpenBSD driver compatibility layer, and POSIX coverage expanded with O_CLOFORK, kqueue with Haiku-specific objects, and more. Filesystem drivers received serious attention as well: NFSv4 got refactors and asynchronous I/O improvements, BFS tuned its free-block scan and query index selection, and the file-data cache now keeps one write queue per disk device — so a large copy onto a slow disk no longer appears to finish instantly only to stall at sync.
Still in the Lab
The ARM64 port now boots all the way to the desktop under virtualization, and one contributor runs an unmerged branch on Apple M1 hardware. Multiprocess WebKit for the built-in WebPositive browser has progressed but is not ready. Neither feature shipped in beta6; rather than rush them into the release, the team kept the immature work on the development line. Lower-level robustness got attention too — the guarded_heap debug allocator was rewritten, and low-memory behavior, a notable concern in a system designed without an OOM killer, now recovers from more failure states than before.
How a 25-Year Project Keeps Running
Haiku, Inc. is a 501(c)(3) non-profit supported by donations, and across this entire release cycle it employed core developer waddlesplash as a contractor — a contract that is still in force. A good share of this release’s stability is, quite literally, purchased time. The project also added one new committer, Zardshard, and reports more than 3,900 open tickets against 16,000 closed ones on its bug tracker. In 2026, with AI-generated code flooding every repository, a 25-year-old project that states it uses no AI-generated code still shipped a near-2x compile-time improvement. The lesson about long-haul open-source desktop development is unchanged: funding, patience, and unglamorous engineering fundamentals.