Your services
Manage accounts, keys, and refresh settings here. Changes are saved in the database.
Drag an account by its grip to change the order, or use the arrow buttons. Order saves automatically and appears on Presto Home and swipe cards on the next poll. Uncheck Enabled to pause a source and hide it on Presto; its settings, key, and position are kept.
Every card on this tab applies to one account only. Settings that apply to every service are on the Settings tab.
Want to see how it works first? Show sample data.
The DASH_DEMO environment variable controls demo mode for this daemon; edit the environment instead of this page.
Saved changes appear on the Presto display on its next successful poll. New readings may take longer if a probe is still running.
Status
Not loaded yet
Everything here is read-only. It refreshes every 10 seconds while this tab is open and the browser tab is in the foreground.
Daemon
Presto devices
Every Presto the daemon keeps a durable record for, by the device ID its setup created. The installed revision is what the device says about itself; it is not a USB hash check. When it differs from the app this daemon serves, the Presto updates itself over the air; only a Presto that cannot (older firmware, or one not yet set up for updates) asks for USB. A device that only sends a client name and a revision appears under Clients below instead.
Daemon release
Whether a newer published daemon exists, from the one registry this installation uses (PyPI for pip and pipx, GitHub Container Registry for the Docker image). The daemon checks in the background about once a day. Opening this page contacts no registry, and nothing here upgrades anything; Check for updates asks the daemon to look again now.
Clients
Every device that fetches the status endpoint. Clients behind NAT, a reverse proxy or Docker Desktop can share one address, so two clients with the same name and address cannot be told apart. A client that has not fetched for a day is forgotten. Nothing about a client is stored.
Accounts
Alerts
Which services are alerting, and which are not. Alerts can be off for every service at once, with the master switch on the Settings tab.
Readers and collectors
Problems
Recent warnings and errors from the daemon. The list is kept in memory only, holds the last 50 entries, and is empty again after a restart.
Log
The daemon's recent log lines, newest first, kept in memory only and gone after a restart. A line that repeats is counted, not listed again.
Settings
These settings apply to every service. Each section is collapsed except the first one.
Home display Applies to all services
Most lines of names for services that do not fit; 0 turns it off.
Fixed by DASH_OVERFLOW_ROWS in this
daemon's environment (in Docker, the .env file). Remove that variable to
change it here.
Set up a Presto Applies to one device
Install the dashboard on a Presto plugged into a computer by USB. You need no copy of this project: this page gives you the exact app this daemon serves, plus a one-time encrypted setup file with the daemon address and device token. Do this once for each Presto. The setup script asks for Wi-Fi locally, so a Wi-Fi password is never typed into this page. A Presto that already updates its app over the air keeps its app: for it, the script changes only the settings.
This daemon generated a new
device token at startup, so the Presto will lose access when the daemon restarts.
Set daemon.shared_token in the configuration first, then prepare a new
download.
Use the daemon computer's LAN address, not localhost and not a container's internal address.
The Presto cannot look up a short
name like this one. A computer usually adds its network's domain to it, but the
Presto does not. Use the full name (for example server.localdomain)
or the IP address.
The setup script asks for the network name and password on the USB computer. The Wi-Fi password is never typed into this page.
Your browser may say
presto_setup.py could harm your device. It says that about any
program file, so it is expected: choose Keep. The file is plain
Python text you can open and read first. It came from this page a moment ago and
holds no password or token: those are in the encrypted file, which only the code
below opens. If you did not just press Prepare download, choose Delete. When
this page is opened over plain http:// from another computer, the
browser may also say the file cannot be downloaded securely; choose
Keep for that too.
Setup unlock code
Type this code into the setup script on the USB computer. It is not inside either download, and it is shown only once. If it is lost, prepare a new download; the device token is not changed either way.
- Your browser has downloaded presto_setup.py and presto_setup.enc. If it asked to allow several downloads, allow them. If one did not arrive, use these links.
- Put both files in one folder on the computer the Presto is plugged into.
- Run
python presto_setup.pythere and type the code when asked. The script installs the app (a Presto that already updates its app over the air keeps its app and gets only its settings), keeps or replaces the device's own settings, and deletes the encrypted file when setup succeeds.
Remote reports Applies to all services
The DASH_INGEST_ENABLED environment variable controls remote reports for this daemon; edit the environment instead of this page.
Remote collectors send observations to this daemon over plain HTTP from other computers. Enable it only on a private network such as Tailscale, or behind a reverse proxy with TLS. A remote token is write-only for one account and report bodies hold no secrets.
Remote reports travel over plain HTTP. On an untrusted network put the daemon behind a reverse proxy with TLS, or use a private network.
Download collector (presto_collector.py)
Accounts that report remotely
Remote reports are off, so the daemon refuses every remote collector, with or without a token. Turn them on above first.
Demo mode Applies to all services
The DASH_DEMO environment variable controls demo mode for this daemon; edit the environment instead of this page.
While demo mode is on, the Presto and the status API show a scripted set of sample accounts instead of the real ones, with their own demo chip. The real accounts are untouched: no provider is contacted, no reading is stored, and a bell tap on a sample account is remembered in memory only. Turning it off brings the real readings back on the next poll, with no restart.
Alerts Applies to all services Alerts on for every service
Alerts are off for all services: no service chirps, lights up or scrolls Home to an alarm. Turn the master switch on to use the settings below.
A service that has used this much of an allowance turns yellow.
A service that has used this much turns red. It must be above the warning percent. At 100% a service is rate limited, as it always was.
Sound is off until you turn it on here: a desk device must not beep unannounced. Tick this box to let the Presto chirp. One chirp for a warning, two for a critical or rate-limited service. A warning that persists does not chirp again, and a recovery is silent. Long-pressing the Presto mutes the sound for a few hours; the screen shows how long is left.
How long the Presto stays muted after a long press, from 0 to 48 hours. Zero means it stays muted until you long-press again. The screen shows a MUTED chip with the time left, so a mute cannot be forgotten. A restart clears the mute.
In quiet hours the Presto stays silent and its light is dimmed. The times are this computer's local time; the daemon decides when it is quiet, so the device needs no clock.
Home scrolls to a service that has just got worse, once the alarm has held for half a minute. It never moves while you are touching the screen, and it brings your own position back a minute later.
It is quiet now: the Presto is silent and its light is dimmed.
Browser sessions Applies to every browser
A browser stays signed in for seven days. If someone else may have signed in with your admin token, sign every browser out, then lock this page and sign in again. A token you set in the configuration file also ends the sessions made under the old one when you change it; a token the daemon generates at each start does not, so this is the way to end those.
Effective daemon configuration Applies to all services
Read-only. These values need a daemon restart, so they are edited in dash.toml or in the environment, not on this page.
About and help Applies to all services
Cloud and subscription sources
Available subscription connectors show current allowance meters in your source list. OpenCode Go reports quota percentages. Ollama Cloud reports dated activity; monthly included and purchased credits are read separately from rolling activity. Codex uses your existing ChatGPT login in the local Codex app. Claude uses a Claude Code terminal quota export. Subscription allowances are separate from API billing.
Order
The order of the accounts on the Services tab is the order of the Presto Home list and of the swipe cards. It saves automatically and applies on the next poll.
Logs and diagnostics
The daemon writes its own log to the console it was started from
(python -m presto_ai_dash.app --config dash.toml --admin). The Problems list on
the Status tab shows the recent warnings and errors without reading the log file.
The device prints its fetch diagnostics to the Presto's serial console.
The help links
Help opens the public documentation site in a new tab. Nothing from this page is sent with the link.
Readings
Setup
Add source
Keys are encrypted in the database and cannot be read back through this page. Deleting a source removes its saved key; past observations remain until retention cleanup.