Public open-source release
Primary near-term goal: publish sources and a reproducible way for others to build and boot. Optimistic that this can happen soon; no hard date. Until then the tree stays private.
Horizon
Categories the project is exploring. Nothing here is promised to ship, on a date, or at a quality bar. The OS itself is still private; a public open-source release is a near-term goal, not a done fact.
No ship dates · not public yet. Horizon items may be cut, merged, or reordered as engineering learns. When a capability is verified in our private trees, it moves to The OS — not this page. Visitors cannot download or run Okei OS today.
Near focus
Active engineering themes
Work in the issue tracker today clusters around these areas — not a guarantee of completion order.
Web emulator depth
Done in-house (Jul 2026): Multiboot2 → interactive bash in browser. Next: Okei Desktop on web guests, full C/WASM opcode core (Phase 2b), faster boots — then share with the release.
Okei Desktop polish
Desktop v1 landed June 2026 for our team; Jul focus — terminal stability (incl. outbound SSH residual), WM chrome, wallpaper/present boot, VirtualBox desktop boot cuts, headed curl okeios.org path (28 Jul), headed win.sh verification.
Install & packaging
Partition-root and UEFI/GPT software gates advanced in July; remaining work is physical hardware evidence, a mature package ecosystem, and a contribution workflow ready for outsiders.
Application landscape
Categories under specification
The table below is a category map only — no feature depth. Platform detail for what exists today is on The OS.
| Category | Examples (planned, mostly unbuilt) |
|---|---|
| Platform | Hardware install validation, package ecosystem, multi-user security, settings, drivers (Wi-Fi, GPU) |
| Desktop utilities | File manager (pre-alpha shell exists); task monitor, disk utility, display manager |
| Productivity | Web browser, email, notes, calendar, media library |
| Office suite | Documents, spreadsheets, presentations, forms |
| Creator's suite | Page design, image edit, video edit, CAD — maker workflows |
| Runtimes | GNU toolchain on-target, Node.js, Python |
| On-device AI | llama.cpp, OpenCode, Hermes agent — design only today |
| Games | Chess (usable), Solitaire + Asteroids (pre-alpha shells, QEMU gates); richer arcade UX still planned |
Windowing vision
Okei Desktop & Aether
Okei Desktop v1 is the local compositor shipping today (panel, 21 registered apps, 1080p, QEMU-tested). Aether is a longer-horizon protocol for network-transparent remote surfaces — same semantics locally or over high-latency links. Research and schema work exist; it is not a product surface.
- Capability-secure surfaces and input (design intent — kernel scaffolding partial)
- Lean protocol design vs retrofitting X11 or RDP
- Research stage — not a product surface
Hardware horizon
Beyond QEMU x86_64
Exploratory targets — none are release-quality ports today. The browser x86_64 emulator is a first-class surface for our CLI bring-up (see The OS), not a public playground and not a substitute for bare metal.
- Raspberry Pi 5 (ARM64) — AArch64 virt and image scaffolds exist; real board serial/SD/Ethernet/HDMI evidence still required
- Older x86 laptops and embedded boards as design constraints, not validated ports
- Phones, wearables, dropped Apple hardware — vision document territory
Quality bar (when apps exist)
Testing policy
Policy: no app feature is “done” without an automated test mapping. Coverage is far from complete across apps.