2026-07-21 21:30:10 -03:00
2026-07-21 21:30:10 -03:00
2026-09-28 01:19:51 -03:00
2025-03-01 11:40:04 -05:00
2025-03-01 11:40:04 -05:00
2026-09-28 18:25:39 -03:00
2025-03-01 11:40:04 -05:00
2025-03-01 11:40:04 -05:00
2025-03-01 11:40:04 -05:00
2025-03-01 11:40:04 -05:00
2025-03-01 11:40:04 -05:00
2025-03-01 11:40:04 -05:00
2025-03-01 11:40:04 -05:00
2025-03-01 11:40:04 -05:00

TaijiOS

Current direction: all-Ziran TaijiOS

The authoritative new plan is a capability-based microkernel OS written entirely in Ziran, using Kryon for its interface. Start with the foundation index for architecture, cited research, feasibility gaps and the staged roadmap. These are planning documents, not a completed OS implementation.

Historical Plan 9 integration

The material below is preserved reference for the previous TaijiOS tree and migration. It does not define the new kernel or relax the all-Ziran target.

Cloudflare Pages

TaijiOS desktop banner

TaijiOS is Kryon Labs' flagship operating system: a bootable desktop OS tree based on the 9legacy branch of Plan 9 from Bell Labs, with Kryon applications preinstalled as the default working environment.

The tree includes Shelf, Rill, Terminal, Inner Breeze, Pass, and the supporting Kryon runtime work needed to boot them together inside TaijiOS. See README for the historical upstream README file.

Bundled Kryon Desktop

TaijiOS is the integration target for the Kryon application stack:

  • Shelf provides the file manager and desktop file surfaces.
  • Rill provides the graphical shell and application launcher.
  • Terminal provides the terminal app (stable command and submodule ID t9).
  • Inner Breeze provides breathing, meditation, and habit tracking.
  • Pass provides stateless password generation.
  • Kryon provides the shared UI/runtime layer used by the applications.

The default QEMU profile opens one Rill desktop immediately. Applications choose their runtime through their launcher; there is no startup flavor or namespace selection. The text profile stays available for low-level OS work.

An experimental Linux application path puts Debian X11 applications in native windows alongside the desktop. The application menu includes Text Editor (xedit) and Eyes (xeyes). Native applications and these launchers share Documents and the desktop's text clipboard. This currently supports a small set of i386 X11 applications; Windows/Wine execution is not implemented. Native and supported Debian apps appear together in the taskbar, and Ctrl+Tab switches between them. Terminal, Files, and Settings use native windows; the panel and menus stay above apps. Debian application displays follow their native window size, rill-open opens documents through the application registry, and About opens as an ordinary window. See the unified desktop notes for setup, commands, tests, and current limits. The current status and remaining plan distinguish implemented features from verified behavior, including the application matrix and the work still needed for Windows support.

Boot Locally

To boot TaijiOS, install qemu, so that you have qemu-system-x86_64 in your path. Then:

git clone https://github.com/taijiosnet/taiji.git
./taiji/boot/qemu

The qemu script builds u9fs in taiji/sys/src/cmd/unix/u9fs and then runs qemu with the right options to boot diskless, using the git clone as the root file system.

Because the VM shares the files with your host machine, you can edit files in one place and see the changes instantly in the other place. For example, you can edit files in your local editor even if you are running tests in the TaijiOS VM. You can run builds of Go binaries targeting TaijiOS on your host machine and then test the binaries in the VM. And you can run more than one VM, all sharing the same file system.

At boot time, the startup disk boot/pxeboot.raw loads a minimal TaijiOS kernel into memory, which then PXE loads a plan9.ini and new kernel over TFTP (provided by qemu). So if you make changes to the kernel, you can boot from ether0!/sys/src/9/pc/9pc to test an as-yet-uninstalled kernel.

The plan9.ini is loaded from /cfg/pxe/525400123456. (That number is the VM's MAC address.) Changes made to that file will be visible on the next VM boot.

Ziran migration

TaijiOS is being rewritten in current Ziran, with plan9-c as the native transpilation path. Rill must be restored as the main desktop environment, entirely in Ziran and using current Kryon. Compiler or runtime gaps belong in Ziran; reusable UI capabilities belong in upstream Kryon; desktop policy belongs in upstream Rill. App submodules contain committed upstream source.

This migration is not complete. The OS still contains thousands of C files across commands, kernel and drivers, boot code, compatibility libraries, libc, graphics, cryptography, networking, and other libraries. Assembly, the native build/bootstrap path, and the remaining application implementations also require an explicit migration and verification path. Passing a library or shell probe does not establish that the OS or desktop has been rewritten.

The Rill shell, panel layouts, settings persistence, stub adapter, Plan 9 platform services, panel clock, Run dialog, Applications menu, Calendar, Settings, and About now use Ziran implementations. A new rill-desktop entrypoint adds the current Kryon panel, live task/launcher snapshots, in-place menus, all four panel edges, autohide, scrolling, item moves and persistence, and available volume/clipboard/session controls. Native desktop overlays use only the client's own window namespace. The converted screens and desktop share a native libdraw application host. Settings uses current Kryon controls for desktop preferences, system control panels, all eight panel configurations, Xfce panel import, display preview rollback, and all nineteen window shortcuts. Saved desktop preferences and panel layouts reload without restarting the new desktop. Desktop file selection, icon layout persistence, group dragging, folder drops, context menus, rename/New Folder dialogs, and file transfer controls now use Ziran and Kryon. Native directory listing, private folder creation, renaming without overwriting, and file/folder clipboard transfers are implemented. Native PNG icons now load through Kryon's Image surface. Native Move to Trash, restore, and empty services now use Ziran, and the desktop Trash browser uses current Kryon. The hosted transfer backend remains C. Native display/input and other missing services still need implementations; their controls remain unavailable. Rio's window snapshot and PID ownership check also use Ziran. Run make rio-ziran-plan9 to generate rio's native sources, then make rill-ziran-plan9-smoke to generate the behavior tests from source and saved IR through plan9-c, compile and link with native 8c/8l, and run them in the private TaijiOS guest. The gate also checks native file and process operations, application and icon registry overrides, and window controls restricted to processes launched by Rill. It builds rio, compiles Rill's generated service objects through its native mkfile, and runs the persistence checks through mk test. It also checks Run history, application matching, categories and recent launchers, Unicode editing, scrolling, session confirmation, clock formatting, Gregorian calendars, month navigation, timestamps after 2038, panel editing, window action failures, clipboard overflow, autohide, wheel ownership, panel JSON validation, shortcut collision detection, concurrent preference merging, exclusive native file leases, stable file selection after refresh, group positions, folder drops, file operation failures, transfer conflicts, wallpaper rotation, held pointer clicks, and display rollback. It renders the converted Kryon screens with native libdraw from source and saved IR and compares their captures. It builds, installs into private guest directories, and renders the actual native Run, Applications, Calendar, Settings, About, and desktop executables through their app/*.mk recipes. PNG checks cover 33 independent reference images across standard color types, depths, filters, transparency, and Adam7 interlace, plus malformed streams, cache eviction, alpha composition, real desktop icons, and native Plan 9 image compatibility. The decoder and native image provider are current Ziran; bounded decompression uses Ziran's native libflate adapter. PNG files are limited to 64 MiB and 4096 pixels per axis; gamma and color profiles are ignored, and 16-bit samples use their high byte. Ziran's compiler regressions also cover wide comparisons, array initialization without adjacent stack writes, aggregate evaluation order, and file size queries that preserve the read cursor. TAIJI_RILL_ZIRAN_SUITES and TAIJI_RILL_ZIRAN_APPLICATIONS can select focused checks; the default runs every suite and all six applications. TAIJI_RILL_ZIRAN_SUITES_ONLY=1 runs native source/saved-IR suites against an upstream RILL_DIR before integrating its commit. This mode omits downstream service builds and application captures; the default gate verifies those too. The native rill-open command and desktop share the Ziran document resolver. It chooses each file's extension independently, preserves literal filenames, retains system applications when the user overrides only part of the registry, and limits Linux document translation to the normalized home directory. The gate also builds this command and checks its actual argv and exit status. Native file and folder Copy/Paste, Duplicate, Move, and Cut/Paste now use Ziran services with staged publication, cancellation, Skip, Keep Both, Replace, and preserved permissions and modification times. Folder copies include hidden entries and empty directories and reject recursive bindings and destinations inside the source. Moves publish the complete copy before removing source entries; changed or protected entries stop removal with an explicit error. Cut/Paste clears its unchanged clipboard selection only after every item moves successfully. Foreign staging entries and newer clipboard contents are preserved. Native Move to Trash saves a checksummed recovery record and the complete payload before removing source entries. The current Kryon Trash browser shows original paths and deletion times, supports restore with collision-safe names, and confirms permanent emptying. Storage defaults to $home/lib/rill/trash with an absolute RILL_TRASH_DIR override. Each private entry records every copied node's identity; damaged metadata, replacement nodes, redirected payloads, and unknown contents are preserved and reported. Saved identities reanchor to the current store after a legitimate filesystem remount. Native source/saved-IR checks cover recovery after releasing the transfer, header and inventory corruption, bound payloads, cancellation before and after publication, and the desktop controls. The browser displays up to 64 entries at a time; restore and empty currently run synchronously. Replace stages the incoming entry completely and preserves the old destination in Trash before publishing without overwriting a newly created entry. It handles files, folders, differing types, batch choices, and Cut/Paste. Changed destinations and overlap with selected sources refuse replacement; cancellation or later publication failure leaves any completed backup recoverable in Trash. Retry now retains completed and skipped items, restarts unpublished copies with a fresh snapshot, and verifies a published destination before resuming removal of unchanged source entries. Recreated source entries and changed copies are preserved. Folder permissions can be repaired before retrying; failed staging cleanup must succeed before another attempt starts. A replacement reuses its published Trash archive after partial removal of the old destination. Cut/Paste retains its original clipboard snapshot across retry and clears it only after complete success. Undo now retains one completed Copy, Duplicate, or Move batch in memory and verifies every result and replacement backup before changing the batch. Copied results go to Trash; moved results return to their original directory, recreating missing parents and keeping both entries when a name is occupied. Replaced destinations return from their verified Trash backups. Undo advances with the transfer polls and can be cancelled and retried after partial progress. Changed trees, redirected paths, and changed backups are preserved and reported. Closing the desktop releases the journal; another completed Copy, Duplicate, or Move batch replaces it. Undo does not provide Redo. Native desktop startup now recovers verified staging copies after their owner exits, preserving partial contents under a visible (partial copy 1) name and keeping both entries when occupied. Fresh homes receive an owner-only Desktop folder before recovery; existing folders, files, and explicitly configured desktop paths are preserved. Recovery uses private receipts tied to the parent, receipt, and staging root identities and the last checkpoint's root metadata. It skips live owners and preserves damaged, unrecognized, or redirected entries with an error. Leftover receipts after publication can be removed without changing the completed destination. It scans the requested directory, does not resume interrupted moves or search nested Trash entries, and does not persist the Undo journal. Recovered copies may be incomplete. The new desktop entrypoint is not yet the boot default: remaining file services, full tray rendering and menus, plugin Properties, notifications, and remaining services still need conversion and parity checks. The full graphical desktop, Rill's other services, Terminal's remaining legacy modules, and the wider OS migration remain unfinished.

S
Description
Design and development for a capability-based microkernel operating system.
Readme
254 MiB
0 Stars 1 Watchers 0 Forks
No results found.
Languages
C 71.6%
PostScript 9.3%
HTML 9.1%
Shell 3.3%
Roff 2.2%
Other 3.9%