What we are building, and why.
Notes from the people making Lisa: the decisions behind it, what changed, and what we got wrong.
Lisa works while you are away
What a proactive operating system does, in scenarios: the printer that sets itself up, the mail you never have to read, the question that arrives with its answer, the update at the quiet hour — and the rules that keep it from ever doing the wrong thing in your name.
Coder: how we are building the best coding agent yet
Coder is where you make a Lisa application by talking about it. Behind its window is the Harness, Lisa's one agent loop, built to be the best coding agent there is — and built to prove it rather than say it. What it does, what makes the loop different, and where it stands.
Lisa for developers: one SDK, one command, no private doors
Lisa's own applications are built with exactly the SDK a stranger gets. What a developer imports, the coder command that builds and checks it, Developer Mode, the road to Harbor — and how much of it is not built yet.
One home, every flavour: how Lisa connects your machines
Desktop, server, touch and smart are four kinds of Lisa. What connects them is a Lisa ID at lisaos.me, and a household that puts a family's machines in the same house. What crosses today, what waits, and what we have not decided.
Lisa Smart: the concept of Lisa at the heart of the home
Lisa Smart is Lisa for the home — a speaker with a small screen and no keyboard, and the hub that detects and connects every smart device on the home's network. Nothing of it is built yet. Here is what we have decided, what is open, and why.
TDD, DDD and BDD were for humans. Here's what we built for agents.
Every methodology compensates for a human weakness. Agents have different ones — so we built oracle-, context- and spec-driven development into the harness Lisa is built on.
Lisa Touch: the concept of Lisa on every touch surface
Lisa Touch is Lisa for every touch surface — phones, tablets, any screen you touch. Nothing of it is built yet. Here is what we have decided, what we have deliberately left open, and why the rest of Lisa is already being shaped for it.
How we built the Lisa desktop, and why
A Rust compositor, a Flutter engine we host ourselves, and one resident Shell — the decisions behind the Lisa desktop, and the ones we reversed on the way.
Harbor: where Lisa's applications come from
Applications on Lisa arrive only in signed sets, on the same channel and under the same root as the OS. How Harbor works, why there is no sideloading, and the store's door we have written but not yet built.
Lisa Core: the daemons that hold every authority
Under every Lisa flavour sits one Rust workspace — the daemons that decide what runs, what is allowed and what leaves the machine. What Core holds, why each authority has exactly one owner, and why it is the one part of Lisa meant to be open.
Lisa's bases: what Lisa runs on, and what it asks of the machine
Lisa is a layer, not a distribution. A base is the Fedora system underneath it, and a written contract decides which machines qualify. Here is the contract, the three bases, and how a machine earns its place.
Lisa Server: its own image, from the same release
Lisa Server is not a desktop with the screen switched off. It is its own signed image, built from the same release as the desktop, installed over any rented box with one command. Why we split it, and what a server carries.
Introducing Bridge: Lisa Server's face in a browser
Lisa Server has no screen, so its whole machine is steered from a browser. Bridge is what the Shell is to the desktop — the system, its updates, its people and the apps it hosts, under one sign-in.
Introducing Lisa
A desktop operating system that writes down what it decides before it builds it — what Lisa is, what it runs on, and how far along it is.