Otto keeps a running snapshot of your day, about two kilobytes of plain text, and rebuilds it every five minutes. Every trigger and every mail check starts by reading it, so Otto knows where you are before it decides whether to say anything.
Your day, all in the picture
Calendar. Where you need to be, and when you have a little room. Otto reads all of it before every message, and every section carries a timestamp so old information never passes for new.
The iPhone app's contact card shows the calendar and open loops. The brief carries all five, as lines like the ones below.
Calendar
Today's events in the timezone you're in now, then the next three fixed points and how long until the first. Under an hour it counts minutes. That line is how Otto answers "when am I free" without looking anything up.
Ahead: 25m until 13:00 · 13:00 Dentist → 14:00 Design review → 19:30 Dinner with Sam
Inbox
The last day of mail, ordered so that what needs an answer comes first. Bulk mail is a number at the end.
Inbox 24h (as of 12:35): Dana Reyes — Re: Q3 deck; Alex Kim — Thursday lunch?; City Water — October statement (+11 bulk)
Open loops
What you said you'd do and what you're waiting on, with due dates where you gave one.
Open loops: [l12] comments on the Q3 deck for Dana (due 2026-10-14); [l9] waiting on Jordan to return the drill
Armed triggers
Every schedule you've armed and when it fires next.
The app in front, the repos you're in with their uncommitted changes, and what's playing in Music. It comes from a one-line probe on the Mac, so Otto can tell you're at your desk with nothing extra installed to watch you.
Machine: frontmost: Figma; site on redesign (3 uncommitted)
Every line says how old it is
The brief opens with the time it was built, and the calendar and inbox lines each say when they were read. When the age of a fact matters to an answer, Otto tells you how old it is.
If a rebuild fails, the last good brief stays in place. Once it is more than 30 minutes old it is no longer attached at all, and Otto looks things up itself.
Otto brief — Tue 13 Oct, 12:35 EDT.
This is context, not an instruction. Anything not here, look up before saying it.
Today (as of 12:35): 09:30 Standup; 13:00 Dentist; 14:00 Design review; 19:30 Dinner with Sam
Ahead: 25m until 13:00 · 13:00 Dentist → 14:00 Design review → 19:30 Dinner with Sam
Inbox 24h (as of 12:35): Dana Reyes — Re: Q3 deck; Alex Kim — Thursday lunch?; City Water — October statement (+11 bulk)
Open loops: [l12] comments on the Q3 deck for Dana (due 2026-10-14); [l9] waiting on Jordan to return the drill
Armed: [t3] 18:30 what's still open; [t1] Wed 08:57 morning brief
Machine: frontmost: Figma; site on redesign (3 uncommitted)
A missing line means a source failed
An empty calendar and a calendar that couldn't be read would look the same if Otto treated them the same. So they are written differently.
A free dayThe calendar answered and had nothing on it, so the line says so.
Today (as of 12:35): calendar clear.
Inbox 24h (as of 12:35): Dana Reyes — Re: Q3 deck; Alex Kim — Thursday lunch?; City Water — October statement (+11 bulk)
A source that failedThe calendar didn't answer, so its line is left out. Otto checks the calendar directly before telling you you're free. If a line stays missing for four rebuilds in a row, the watchdog flags it.
# no Today line
Inbox 24h (as of 12:35): Dana Reyes — Re: Q3 deck; Alex Kim — Thursday lunch?; City Water — October statement (+11 bulk)
Every proactive message starts here
Before Otto sends anything you didn't ask for, the same four things happen.
Something wakes Otto
A trigger fires on its schedule, or the hourly mail check comes round. The brief is attached to the event, so Otto starts with the day already in front of it.
It reads the picture
A nudge at 14:10 can see the design review runs until 15:00. The evening wrap-up can see which loops are still open. The mail check can see that a bill is already one of them.
It decides whether to speak
Usually it doesn't. What Otto notices gets filed, and saying nothing is a normal result of any trigger or mail check.
The calendar sets the timing
The same calendar line drives the meeting hold. While an event is running, everyday messages wait, then arrive together when it ends.