What's new in freddy: week of Jul 27, 2026
In short
- Your AI stops reporting an older date as empty when the records were there all along.
- The catalogue of metrics it reads at the start of a session is about half the size.
- The Android update is live on Play, with battery guidance for your phone brand.
- A source stuck mid sync can always be removed now.
- The support chat has a consent toggle for sync troubleshooting, off unless you turn it on.
- Apps behind Apple Health and Health Connect answer properly, and records dated years ahead are refused.
Older dates stop coming back empty
freddy's query tool takes one date range at a time and returns the newest records first. Ask your AI to compare two dates a few weeks apart and it tends to reach for a single wide range bracketing both. If that range holds more records than one response can carry, the oldest end gets cut, which is exactly the date that prompted the question. Your AI then reports that date as empty while the records sat in the database the whole time.
A truncated response now names the calendar dates in the part it left out that do hold records, so your AI can see which days are still waiting rather than calling them missing. The tool description also states plainly that two separate dates need two separate calls.
A lighter catalogue at the start of every session
Every session begins with your AI reading the list of metrics your account holds, because metric names are source specific and cannot be guessed. That list was keyed by metric, unit, source and device, so one metric name fanned out across every watch, phone and app that had ever written it. On a busy Apple Health account it ran to hundreds of lines before you had asked anything.
Entries are now collapsed to one per metric and unit per source, with the devices listed inline, grouped under a single heading per source, and paged rather than running on. On the account it was measured against it came out roughly half the size with every metric name still accounted for, which leaves more of the conversation for your actual question.
The Android update is on Play
Health Connect background sync used to stop when another app had written a record it could not read. It skips that record and carries on now. The Android app also detects battery settings that block background syncing and shows the steps for your phone brand, since those settings differ a lot between manufacturers. The status telling you your history is still importing now appears on Android too, the same as on iPhone.
A stuck source can always be removed
A source that was mid sync, or stuck reporting that it was syncing, refused to disconnect. That is the wrong behavior for a failing source, which is precisely when someone wants it gone. Removal now always goes through, and any sync work still running for it is cancelled and cannot write anything back afterwards.
A consent toggle for support
Working out why a source stopped syncing needs a look at your sync state. The support chat now carries a toggle for that, off unless you switch it on, granting a deliberately narrow view: which sources are connected, the most recent sync attempts and what class of error they hit, and per metric record counts and date ranges. No readings, no values, no device names.
Every time that view is opened a line lands in your own chat thread saying so, and switching the toggle back off ends the access.
Smaller fixes
- Apps whose data reaches freddy through Apple Health or Health Connect, such as Samsung Health, Sleep Cycle, MyFitnessPal and Peloton, used to fail with a generic error when you asked your AI to connect or sync them. They now get a real answer naming the hub that carries their data, and it is platform accurate.
- A source app writing the wrong year could store a record dated years into the future, which then counted as the newest thing in your history, so a question about your latest weight answered from a phantom. Records dated more than a couple of days ahead are refused as they arrive now, for both Apple Health and Health Connect.