Done: shipped in 1.1

What we'd like to build before V2

Grouped by theme, not by version number. This is what we want to build; what actually lands next, and in what order, is shaped by what the community asks for once V1 is in real use. Bug fixes and community-response polish are a fixed slot in every release, and well-argued requests can jump ahead of anything below.

Timeline & navigation

New providers & integrations

Scores & actions

Personalization & data

On request (community-driven)

Beyond V1

V2 plans aren't published. They'll come into focus once V1 has a few months of community use behind it. That feedback is what shapes the V2 pitch, so committing now would be premature.

Score catalog

Twenty scores ship bundled at launch (plus Apple Calendar and Reminders via EventKit). Beyond those, new scores ship continuously across all V1.x releases, sequenced by community signal, so the most-requested gets prioritized.

Bundled at launch

Upcoming (community-signal)

Grouped by where each tool lives in your stack. Sequence is driven by community signal: most-requested gets prioritized. And, honestly: I can't run all of these myself, so scores for tools I don't have are built and verified together with people who do. If you use one of these, a sample payload or a round of testing from you is often what moves a score from "planned" to "shipped".

Suggest a score (or build one) by opening an issue or PR on caereforge/tempo-scores, or starting the discussion on the community.

Tempo utilities

Alongside the app, we also ship a small catalog of utilities: macOS Shortcuts, AppleScript snippets, helper scripts, and lightweight plugins. Some feed events into Tempo; others are just handy on their own and not tied to Tempo at all. The first entry is the latter kind, a small convenience on the downloads page (a Shortcut to copy message:// deep links from Apple Mail). More land over time as the catalog grows.