What's new in freddy: week of Jul 20, 2026

2026-07-26

Four changes stand out from the week of July 20: a fix for Apple Health syncing that had stalled part of the metric catalog on iPhone, a read-only Personal API in beta, install buttons that replace the copy-and-paste setup step, and recognition for well over 150 more apps that write into Apple Health and Health Connect.

Apple Health syncing catches back up

On iPhones with a lot of history to work through, an incremental sync could spend its entire budget on one heavy metric type and never reach the rest. The visible effect was confusing: steps and heart rate kept arriving, so the connection looked healthy, while most of the catalog quietly stopped moving forward.

Each metric type now gets its own share of the work, so no single heavy type can crowd out the others. Accounts that were affected recover on their own over a few days of normal use. There is nothing to re-import and no need to reconnect.

Health permission prompts also stopped appearing during background syncs. They now show only while the app is open, so a background sync can no longer sit waiting on a prompt nobody is there to answer. Both fixes are in version 1.0.4 on the App Store.

A read-only API for your own data

freddy's main path is an MCP connection, which is what your AI client speaks. Not everything is an AI client, though, and the Personal API covers the rest. You create a key in the dashboard and read your own data over plain HTTP: your normalized metrics, the catalog of metrics and units you actually have, your connected sources, and your profile.

It is read-only, so a key can see your data but never change it or your account. That makes it a reasonable fit for a script, a home dashboard, or anything else that wants numbers rather than a conversation. The full reference lives at freddy.coach/api-docs.

The Personal API is in beta, so access is requested from the dashboard.

Installing takes one click

Connecting freddy to an AI client used to mean copying your personal MCP URL out of the dashboard and pasting it into the client's connector settings. That step is now a button. Claude gets a deep link that carries the URL across, and ChatGPT opens freddy's app listing. The copy-and-paste path still works for clients that need it, and for anyone who prefers it.

Grok also joined the list of AI clients with their own setup instructions, alongside Claude, ChatGPT, Perplexity, and the command-line clients.

More of your apps get recognized by name

Data that reaches freddy through Apple Health or Health Connect arrives stamped with the name of whichever app wrote it. freddy recognized only a short list of those names, so plenty of real sources showed up as an unfamiliar package name or a bare string.

That list is now much longer. Entries resolve to the actual app where the name is known, and sync or relay apps are labeled as such so it is clear the data passed through something before it landed. What gets ingested has not changed, only how it is attributed and displayed.

Garmin history import handles Mac exports

Garmin's API only exposes a limited backfill window, so the data export Garmin gives you is the way to bring older history in. Uploading that export from a Mac could fail, because macOS quietly adds hidden sidecar files to the ZIP that the importer tried to read as health data. Those are skipped now.

The per-import file cap also went up, and a partial import now reports itself as partial rather than as a clean success, so you can tell when something did not make it through.

Smaller fixes

Coming next

The Android app is due the same "still importing your history" status that Apple Health already shows, plus a prompt to exempt freddy from battery optimization so background syncing is not throttled by the system.