All pages

Docs · Configuration

Updates

Availability: macOS. Linux and Windows have no update channel yet — see Platforms.

How TRMNLY replaces itself with a newer build, and how a build can be given a deliberate expiry date instead.

Two separate things live here because they're the same switch pointed in opposite directions: a normal build keeps itself current forever, and a time-limited build refuses to update or to keep running past a date.

Normal builds: auto-update

Updates are delivered by Sparkle and signed with an EdDSA key. A build only accepts an update whose signature matches the SUPublicEDKey compiled into it, so a feed that has been tampered with — or one signed by someone else's key — is rejected rather than installed.

Two channels, one appcast file each:

Channel Feed
Stable https://trmnly.dev/updates/stable/appcast.xml
Beta (tip) https://trmnly.dev/updates/tip/appcast.xml

Pick one in Settings → Updates. The same pane sets the mode: Off, Check and notify, or Download and install.

In a shipped release build, automatic checks are on. TRMNLY checks about once a day and downloads in the background. When a new version is found or downloaded, a small prompt opens at the top right of the front window with Install and Relaunch, Later and (for a version not yet downloaded) Skip. It never takes focus: Return and Escape keep going to the terminal you're typing in until you click the prompt. Later leaves the update to install when you next quit. Settings → Security shows the active feed URL and a short fingerprint of the signing key, so you can confirm the app is tracking the host and key you expect.

Local builds never self-update. Debug and ReleaseLocal compile with automatic checks off, because they aren't Developer ID signed and must not be able to swap themselves for a shipped build. This is a build setting (TRMNLY_SPARKLE_AUTO_CHECKS), not a preference — you can't turn it on by accident from the UI.

Checking by hand

TRMNLY → Check for Updates… answers in the titlebar pill at the right end of the window: "Checking for Updates…", then "No Updates Available" or the update itself. Settings → Updates → Check for Updates Now shows its answer under the button: checking, "You're up to date" with the version, an available update with Install Update, or "Couldn't check for updates:" and the error.

  • If an update already downloaded in the background and you closed its "Restart to Complete Update" notice, Check for Updates brings it back.
  • If a background check is still running, the pill shows "Checking for Updates…" and runs yours as soon as that one finishes.

Your licence and updates

A desktop seat ($99) includes a year of updates; every version released in that year keeps working on your seats for good. Once the year is up, Check for Updates offers only versions released inside it, so the app never installs a version it would then refuse to run. Renew at trmnly.dev/app/licence (Renew updates · $69 a seat) and newer versions are offered again. Early-access accounts have no seat limit and no end to updates. See trmnly.dev dashboard.

When the app won't open, the access window names the reason:

Title What it means What to do
Sign in to use TRMNLY No account signed in on this Mac Sign in with trmnly.dev or Continue with GitHub
Waiting for approval The account isn't approved yet Wait; the window unlocks on its own (Check Now to re-ask)
Your updates have ended This version was released after your year of updates ended; the message names the last version your licence covers Renew…, or reinstall the covered version
All seats are in use Every seat already has a Mac Remove a Mac on the Licence page (Remove this Mac) to free one
TRMNLY can't confirm your access trmnly.dev unreachable for more than 7 days Try Again once online

Use a Different Account signs out and starts over. The same window appears if this happens while the app is running. Signing out with trmnly account logout, or revoking this Mac from trmnly.dev, ends access on the next launch rather than after the offline grace.

If updates never appear

  • Your updates have ended. See above: the feed offers nothing newer than your licence covers until you renew.
  • You're on 0.1.45 or earlier. Those builds have the old updates.trmnly.app host compiled in and will never find the current feed. Install a newer DMG by hand once; from 0.1.46 on it's automatic.
  • You're on a time-limited build. Updating is disabled outright — see below. Settings → Updates says so.
  • The channel is empty. An appcast with no entries is a valid "you're up to date", not an error.

Time-limited builds

A build handed to an outside tester can carry a hard stop date. After it, the app refuses to launch.

This is not a licensing system — there's no server, no activation, and no way to revoke a build that's already out. It's a timer, sized for the case it exists to serve: giving someone TRMNLY for a fixed window rather than forever.

Recognizing one

The About panel (TRMNLY → About) shows two extra rows on a time-limited build and neither on a normal one:

Expires        February 6, 2027
Licensed to    Jane Tester

The date turns amber inside the last two weeks.

What the tester sees

  • Until 14 days out — ordinary TRMNLY. No prompts, no nagging.
  • From 14 days out — one notification per day. Inside the last 7 it bypasses quiet hours.
  • After the date — one modal at launch, then the app quits. There is no "continue anyway".

A session that's already running when the date passes is not killed. The check runs daily and shows the same modal, but nothing in flight is torn down — quitting and relaunching is what actually enforces the stop. trmnly-code is gated identically, so an expired build doesn't leave a working headless agent behind.

Why it can't just be edited out

The date lives in the app's Info.plist, which is sealed by the code signature. Changing it invalidates the seal, and macOS refuses to launch the bundle at all. The enforcement is the OS's, not TRMNLY's — nothing in the app has to detect the edit, because the app never gets to run.

Setting the system clock back doesn't work either: TRMNLY records the latest date it has ever seen and evaluates against that.

Updates are off, deliberately

A time-limited build has automatic checks disabled and the manual paths — the menu item, the keybind, the Settings button — disabled with it. If it could update, it would replace itself with an ordinary release within a day and the expiry would never fire.

The consequence is that a tester gets no fixes for the life of the build. That is the trade: when it expires, they get a fresh one.

If a build expires early

A clock that jumps forward — a dead RTC, a restored VM snapshot — records the bogus date and the build stays expired even after the clock is corrected, with nothing in the UI explaining why. Recovery is to drop both copies of the recorded mark:

defaults delete com.willschulz.trmnly trmnly.buildExpiry.highWaterMark
security delete-generic-password -s TRMNLY.Anthropic \
    -a TRMNLY.buildExpiry.highWaterMark

The keychain account may carry a rotation suffix, in which case security dump-keychain | grep buildExpiry finds the real name.

Cutting a build

Both kinds come from one script:

dist/macos/release.sh                                      # a real release
dist/macos/release.sh --expires 6m --licensed-to "Name"    # time-limited

--expires takes 6m, 1y, 90d, or YYYY-MM-DD. A time-limited build is signed, notarized and stapled exactly like a release — it installs with no Gatekeeper warning — but it is never uploaded and never gets an appcast entry. Artifacts are named TRMNLY-<version>-test.dmg so the two can't be confused.

Bump MARKETING_VERSION / CURRENT_PROJECT_VERSION first: Sparkle compares build numbers, and a version that's already published is a silent no-op. A version consumed by a time-limited build shouldn't be reused for a public release either, or the tester's copy and the public one claim the same version.

Write the version's notes in CHANGELOG.md before cutting it, too. The release script renders that section into the appcast, so the update popover shows what changed; the same file feeds Help ▸ What's New and the Linux and Windows About dialog (scripts/changelog.py). A version with no section ships without notes rather than failing.

See dist/macos/SIGNING.md for the signing, notarization and appcast setup this assumes.