Lisa Blog

Lisa works while you are away

· Flakerim Ismani
proactiveassistantroutinesdesktopdesign

There is a person who cleans the office where Lisa is made. We leave in the evening with cups on the desks and cables on the floor, and in the morning everything is back in its place. Nobody briefs her. Nobody opens a chat window and types please tidy the office. She knows the house, she does the work, and we hear from her only when something needs us — a key that has gone missing, a plant that is dying.

That is what we want from the operating system. Not an assistant you summon and prompt, but a desktop that does the day’s work on its own and tells you afterwards. This post is about what that means in practice, scenario by scenario, and about the rules that make it safe enough to leave running. The law behind it is on the specification site, at /system/proactive; as always, that page says what is built and what is not yet.

Scenario 1 — the printer

You bring a printer into the room and plug it in. On most computers the next twenty minutes belong to a driver download, a setup wizard and a web form. On Lisa, nothing asks you anything. The printing authority sees the device appear, speaks to it in the language modern printers speak without a driver, learns its paper sizes and whether it prints in colour, adds it under its own name, and prints one test page so that the first page you need is not the first page it has ever tried. Then one note appears at the right edge of the desktop:

HP LaserJet M15 set up; test page printed. — Make it the default · Open Printers

Your PDF printer stays the default until you say otherwise, because you said that is what you want, and a device that walks in does not get to change your settings. If the printer is one of the old ones that still needs a driver Lisa does not carry, the note says exactly that — not supported: needs a filter this release does not ship — instead of a spinner that never ends.

Scenario 2 — the mail you never read

You sit down at eight. The column at the right edge already holds the morning brief:

Overnight. 14 mails arrived; one needs you (Alban, about tomorrow evening). Your Thursday meeting moved to 11:00. The update to 2026.11.02.1 installed at 03:10; the printer is ready. Three newsletters were folded into Updates.

You did not read fourteen mails to learn this. Lisa’s Mail application has a background service that receives mail whether or not its window is open, and the brief is assembled from what the service knows and what the other applications report. The judging — which of these needs a person? — is done by a small model that runs on your own machine. Your mailbox did not leave the computer to be summarised.

Scenario 3 — the question that carries its answer

One of those mails is from a friend: beers tomorrow evening? It does not sit in an inbox waiting to be found. It arrives as a card:

Beers tomorrow evening? — Alban Reply: “See you tomorrow evening.” · Yes, send · No

The reply is already written, and it is on the card, so what you send is what you read. One tap sends it in your name. No is remembered for this thread. Nothing was sent until you pressed, because sending mail in your name is one of the acts Lisa never does unattended — not because the model is bad at it, but because the rule is written into the system and an email cannot talk its way past it.

Scenario 4 — the mess on the desk

Over a week a desktop collects screenshots, a Downloads folder collects installers and PDFs, and the Trash collects everything else. These are the chores. Lisa files downloads by kind and month, puts screenshots and recordings away by day, and keeps the Trash from growing forever — each one a routine you can see in Settings, each run a single line in the ledger, each with an Undo that actually puts things back for a week. The Trash is the exception that proves the rule: it is never emptied on its own. A card says 1.2 GB in the Trash is older than 30 days — Empty · Keep, and your tap is the act.

Scenario 5 — the update at the quiet hour

An update is ready at four in the afternoon. Lisa does not interrupt the presentation you are giving. It downloads, waits for the quiet hours you set (two to five in the morning by default), checks that nobody is signed in or that the session is idle and that nothing is recording or presenting, installs, restarts, and leaves one line in the brief: Updated to 2026.11.02.1 at 03:10. If it cannot prove the moment safe, it does nothing forced and asks again in the morning.

Scenario 6 — the things you plug in

A camera appears and is ready in Meet and in the Camera application; a phone appears and a card offers to import this week’s photos; a keyboard reconnects after a restart before the login screen is drawn. The principle is the same each time: a device Lisa knows is set up end to end without a question, and you are told afterwards.

The rules underneath

None of this works without rules you can read, so here they are.

Lisa acts only through the applications. Every Lisa application declares what it can do as tools — Mail can read, search, send; Files can list, move, preview; the printing authority can print and cancel. The assistant has no powers of its own. What it can do is exactly what a person can do in that application, no more, which also means that when the application changes, the assistant’s abilities change with it.

Consent has tiers, and the tiers are enforced by the system. Reads are silent and logged. Writes show a chip. Nothing destructive ever runs unattended. These are not instructions in a prompt; they are checks in the bus the call travels on, and content that arrived from outside — an email, a web page — cannot raise its own privileges however it is phrased.

Routines come in two kinds. The system’s own chores are shipped with Lisa, have no model in their chain, and do and tell. Routines you author (“every evening, draft replies to mail that asks me a question”) may read freely and write within a standing grant you made when you created them. Anything that reaches outside the machine, costs money or cannot be undone stops at a card.

Every routine has a dial. Do and tell, Propose, or Silent. You move it in Settings › Routines, next to the routine’s trigger and its last run. The dial changes what you see; it never changes a tier.

Local first. The decision step runs on your machine. A cloud model joins only if you add one yourself, with your own account, and then only for what you point it at.

Every refusal is a sentence. When Lisa will not do something, it says why, in the window and in the journal. A system a person can debug is a system an assistant can explain.

Where this stands

Honesty is the one habit we do not break on this blog. Today the Assistant is summoned, not scheduled; the first routines — device setup with the printer test page, the morning brief, the mail card — are being built this week, and the Files and Mail background services that make the headless parts possible landed in the last days. Each sentence above turns true on the specification pages only when it has been proven on a real machine, and the release notes say which ones did. If you want to watch it happen, the pages are public: /system/proactive, /system/agent, /system/printing.

The office is a mess tonight. We are building the person who tidies it.

← All posts