Writing action commands in Tempo
How to template Tempo's action buttons with ${...} placeholders: event fields and metadata, shell quoting for terminal commands, running scripts on a remote host, and opening links in a specific browser.
Notes from building Tempo.
How to template Tempo's action buttons with ${...} placeholders: event fields and metadata, shell quoting for terminal commands, running scripts on a remote host, and opening links in a specific browser.
Tempo v1.1 is here: a new log-line timeline, tags and emojis, TLS ingestion, a security panel, new sources with dedicated scores, and the new Caereforge theme.
Tempo is AI-assisted, but not vibecoded. Here's the difference, with concrete examples from how I built it.
Tempo now speaks CalDAV natively, experimentally. Your Fastmail calendars show up in the Agenda without going through Apple's Internet Accounts.
How to bring your Todoist tasks into Tempo with a lightweight polling script and a purpose-built score.
Scripts and Hazel are umbrellas: one parent score covers every sub-source underneath. How that works, how deep it goes, and how it differs from UniFi grouping.
A high-level look at how Tempo v1 is structured, and a more detailed look at the security posture. Aimed at the technical reader downloading v1 today.
The New Token sheet asks for a provider identifier. What it is, what to type for the bundled sources, and what to type for your own scripts.
How to add a custom action button to a source's events: open a log file, copy an IP, or jump to a terminal at a hostname. One JSON file, no relaunch.
Honest notes on Tempo's rough edges. The Score Editor still lags on large scores; action editing and reminder write-back landed in 1.1; calendars read-only.
Three independent integrity layers stand between the Tempo DMG on your Mac and what we built. How each works, when to verify the SHA-256, and why we publish it.
Tempo v1 ships today as freeware: a native macOS event hub that puts every webhook, backup, monitor, and calendar entry on one timeline. Local-first, LAN-ready.
UniFi Protect joins UniFi Network as a built-in source. Tempo renders the motion thumbnail inline, with a bounded image cache so the database stays sane.
Tempo doesn't know about your specific tools. It reads the JSON payload you send and adapts the UI to whatever fields are there. The sender writes the buttons.
A note on the musical name behind Tempo's building blocks, and the scores shipping at launch.
Tempo v1 will ship as freeware, forever. Here's how the community will shape what comes next, and an honest look at the costs behind it.
Before launch, a clear look at what Tempo deliberately isn't, and why that matters.
An introduction to who I am, why I built Tempo, and the philosophy behind it.