Okei Windows polish
Compositor, terminal, mouse cursor, multi-window stress. Desktop v1 exists; production quality does not.
Horizon
Categories the project is exploring. Nothing here is promised to ship, on a date, or at a quality bar.
No ship dates. Horizon items may be cut, merged, or reordered as engineering learns. When a capability appears in integration tests, it moves to The OS — not this page.
Near focus
Active engineering themes
Work in the issue tracker today clusters around these areas — not a guarantee of completion order.
Shell & editor reliability
Bash parity, PTY consistency, Vim keyboard path, writable scratch workflows.
Kernel fundamentals
UID enforcement, fault containment, OOM behavior, signals — foundation before multi-user claims.
Install & reproducibility
Cleaner build graph, disk install path, contributor onboarding ahead of any public release.
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 | Installer, package manager, multi-user, settings, drivers (Wi-Fi, GPU) |
| Desktop utilities | File manager, 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 GUI exists as shell; solitaire, asteroids planned |
Windowing vision
Okei Windows & Aether
Okei Windows is the local compositor shipping today. Aether is a longer-horizon protocol for network-transparent windows — 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.
- Raspberry Pi 5 (ARM64) — planned, not shipping
- 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.