The dashboard
A web view of what Otto keeps on your Mac, read live by your browser with a token you approve.
The dashboard shows what Otto keeps on your Mac: memory, people, open loops, money, trips and the status of every moving part. It has no data of its own. Your browser fetches each page straight from your Otto over Tailscale Funnel, so the site that serves the dashboard never sees what it shows.
The Dashboard button at the top of this site opens a hosted copy. It is the same app, and it still talks only to the Otto you pair it with.
What's in it
- Overview. Today's brief, open loops and anything that needs a look.
- Chat. Your thread with Otto, from the app and Telegram.
- Memory. What Otto remembers, as a list, a graph or a search.
- People. Who's who, in your own words.
- Loops. What you said you'd do, and what you're waiting on.
- Money, Trips and Packages. Spend from receipts and bank mail, bookings in local time, parcels on their way.
- Activity. Proactive messages, capability changes and background jobs.
- Status. The same rows as
otto_status, each stamped with when it last checked in. - Settings. What Otto is allowed to do on its own.
- Devices. Every paired app and dashboard, and what each one can do.
Each page reads one source on the Mac. When a source is missing, only its own page is empty, and Otto can set it up.
Connecting it
You need Otto running on your Mac, Tailscale with Funnel allowed on your tailnet, and Telegram or the iPhone app to approve the browser. The setup page walks through it and remembers where you left off.
Turn on Funnel
Funnel publishes Otto's /app port over HTTPS under your tailnet's name. Otto
can do this for you: ask it to turn on Tailscale Funnel for /app on port 10000
and tell you the URL. The URL ends in .ts.net.
Allow the dashboard
Your Otto answers only the dashboards it has been told about. Allow one by its origin, on the Mac:
bun otto/dash.ts allow https://app.example.com
bun otto/dash.ts list
bun otto/dash.ts deny https://app.example.comLocal and *.vercel.app preview origins are allowed for 24 hours at a time.
Pair
The dashboard shows a short code. Send pair <code> to Otto on Telegram or in
the app, and Otto answers with what is asking: the origin it claims, the access
it wants, the browser and where it is connecting from. Approve only if the code
is the one on your screen. A code is good for five minutes, and typing it again
replaces the older buttons.
Nothing on the dashboard's side can make your phone buzz. The pairing request is reachable from the internet, so it stays silent until you send the code yourself.
Read-only or read and control
| Read-only | Read and control | |
|---|---|---|
| Can | Open every page | Also send messages, change settings, snooze, close loops, mark packages delivered, refresh the memory view and control a live call |
| Lasts | 90 days | 12 hours |
| Kept in | This browser | This tab only |
A browser that asks for control can still be approved read-only. Every token
works only from the origin it was paired on and only under /app/dash/, so a
dashboard token can't reach the iPhone app's routes.
What leaves the Mac
Every response is an explicit pick of the fields behind it, so a field added to a store later never reaches a browser by accident. Keys that must never leave the Mac are refused outright, and the tests sweep every response for them.
The dashboard itself runs under a strict content security policy, with no third-party scripts and no analytics. Once paired, it narrows its connections to the one Otto it paired with.
Removing a dashboard
Remove it from Devices, or from the Mac:
bun otto/apptokens.ts list
bun otto/apptokens.ts revoke <id>To host your own copy, deploy the repository above to its own origin, allow that origin on your Otto, then pair from its setup page.