It works when you don’t.

A trigger, an instruction written in plain English, and a list of what it is allowed to touch. It can run on a schedule, a set number of minutes before a calendar event, when a recording starts, when a meeting ends, or only when you press the button. Each one is a plain markdown file in your vault you can open, edit, or delete.

You can connect Gmail, Outlook mail, Notion, and web search. Two separate settings control a routine: one covers your machine — whether it can touch files and run commands — and one covers change, from read-only, to stopping and asking you before every action, to acting on its own. New routines start manual, sandboxed, and read-only. Every tool in a connected account is classified read or write by hand, anything unrecognised counts as a write until someone reviews it, and the limits you set are applied to the request before it leaves your Mac.

No. Routines run with the laptop shut. That is the point — the work that has to happen at 8am happens whether or not you are at the machine.

Yes. A routine can POST a finished meeting to any endpoint, including localhost. Requests are signed and retried, and you choose what goes in the body.

Every run is logged with what triggered it, which tools it called, and what it cost in tokens. Test runs are always read-only, so you can watch a routine work before you let it change anything.