A capability-native operating system, built for agents.

Capabilities, not permissions.

At the bottom of os0 is kore, a capability-native microkernel — built from the first line for a machine running agents, not for a general-purpose desktop with security patched on top.

An agent holds a capability or it doesn't — never a rule checked at runtime, an unforgeable token that is the access. Broader capabilities derive narrower ones: a project-wide grant can be split into single-file, single-action slices, each one traceable back to something a person granted on purpose. There's no ambient authority sitting behind it to escalate into — no wall to climb, because there's nothing outside the capability to escape to.

Every chip, scheduled like threads.

os0 treats CPU, GPU, and NPU as one pool of compute — a heterogeneous scheduler places work wherever it runs best, weighed against the cost of moving data between them.

Agents run in parallel, not queued. Context loads and evicts on the fly, interrupts included, the way a kernel schedules processes instead of programs. A hot-swappable grammar engine keeps tool calls syntactically valid at roughly 2× the throughput of llama.cpp's constrained output — no malformed calls, no latency tax for avoiding them.

Most NPUs ship locked behind whatever narrow stack the OEM decided to support. os0 is built with first-class NPU support — the efficient silicon already sitting in the machine gets scheduled like any other processor, not stranded behind a driver nobody can use.

Nothing leaves unless you say so.

Every agent, every model, everything the system has learned — encrypted at rest, functional offline.

Cloud is a capability, not a default: routed only when someone with the authority grants it, scoped to that one request. Nothing acquires standing permission to leave the device — a request expires the moment it's answered.

Gets better at being yours.

Without shipping your data anywhere to do it.

os0 fine-tunes LoRA adapters directly on-device, using a lightweight method that runs while idle.

Every change is tested before it's kept, and adapters hot-swap live, so personalization never requires a restart.

Every surface, yours to rebuild.

The interface layer runs on WebAssembly — built from HTML, CSS, and JS instead of a fixed set of OS-native widgets, so nothing about how os0 looks or behaves is locked to a factory default.

Rebuild any surface, not just theme it — the desktop, the window chrome, the controls, all as flexible as a webpage, because they are one. The same runtime means a browser page can run as a first-class native app instead of a tab inside another application — there's no longer a real difference between "a website" and "an app."