What's new in freddy: week of Aug 10, 2026
In short
- freddy now sends a notification when one of your sources stops syncing, and it names the source.
- Suunto workouts bring the route you recorded, not just the summary numbers.
- Garmin's history permission arrives switched off on their consent screen, so freddy names it before you authorize and offers a Reconnect to sources that already missed it.
- Large Garmin data exports import their full activity history instead of dropping it.
- A new recipe walks through a triathlon plan that adjusts itself every morning.
- Claude Code and Codex have their own setup rows, each with one command to copy.
Notifications when a source goes quiet
A source that stops sending data is the failure mode you are least likely to catch. Nothing breaks, nothing errors, the data just stops, and you find out weeks later when you ask a question and the answer stops short.
freddy now watches for that and sends a notification naming the source that went quiet, rather than claiming your whole account went dark. Naming it matters: when the job fired against production, more than a quarter of the people it would notify had other sources delivering normally at that moment, so an account-level message would have sent them hunting for a fault that was not there.
Notifications arrive in the iOS and Android app, and the category can be switched off in Settings or from the dashboard.
Suunto workouts carry the recorded track
Suunto workouts used to arrive as summary numbers, so a run was a distance and a pace with nothing about where it went. The recorded track now comes through as well, latitude, longitude and altitude across the workout, which makes questions about place answerable: how a repeated route compared week to week, or where the climbs on a session actually landed.
Existing workouts fill in as they sync, so older sessions catch up on their own.
Garmin history, and the permission that controls it
Garmin's consent screen carries a Historical Data Export permission, and it arrives unticked. Without it Garmin refuses every request for data recorded before the day you connected, so a connection could look perfectly healthy, sync new data fine, and have no history at all, with nothing on screen explaining why. Most people in that position never declined anything, they accepted a screen of defaults.
freddy now names that toggle before you authorize, on first connect and on reconnect. Sources already in that state carry a Reconnect button next to the explanation instead of only a diagnosis, and granting the permission re-runs the backfill.
Large Garmin data exports keep their activities
freddy can import the data export Garmin gives you, which reaches back further than the API does. That import refused any single file over a size limit, and the one file Garmin ships whole rather than in dated chunks is your activity history, so an account with years of training behind it lost the activities while everything else imported fine.
Oversized files are now read piece by piece. If an earlier import landed without your activities, re-upload the export and they will come through.
A new recipe: a triathlon plan that adjusts itself
Hold your training plan in a project, check it each morning against what your body actually did, and move today's session when the plan and reality disagree. The recipe walks through the whole loop, including the part most plans skip: noticing the sessions you quietly did not do.
It needs a source for training sessions and one for sleep and recovery, plus a calendar connector if you want the week rewritten for you rather than just proposed. The recipe is at freddy.coach/recipes/adaptive-triathlon-plan.
Claude Code and Codex have their own setup
Both are now their own rows in the connect-an-AI picker, each with a single command to copy and run instead of an MCP URL to place by hand.