Skip to content

v0.4.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 29 Oct 13:02
· 87 commits to main since this release
v0.4.0
ee0d40a

The coach that knows you. runcoach now reads your habits from your own history, shows what it has learned about you on a new You tab, feeds that into every answer, and takes questions in your own words.

uv tool install git+https://github.com/edxleon/runcoach-ai@v0.4.0
runcoach serve

Your week, on your days

  • Without a profile, the planner reads from the last eight weeks with running (looking back half a year):

    • how many days you run,
    • which weekdays,
    • your long-run day.

    Every value says where it came from: "long run on sat - your longest run fell on sat in 8 of 8 weeks".

  • After a pause it reads the weeks before the pause, not the empty weeks of the pause.

  • A weekly other sport (a gym Tuesday) keeps the quality runs off that day and the next. If that leaves room for only one quality session, the week has one.

  • Someone who runs twice a week is planned two days, not three.

  • A week with one quality session gets the one that is due: VO2max until the zone-5 stimulus is set, then threshold, or the measurement.

What the coach has learned about you (new: the You tab)

  • Each item comes with the evidence it rests on:
    • your running days, weekdays and long-run day,
    • a weekly other sport,
    • how consistent you are,
    • your intensity pattern over 28 days,
    • the VO2max trend,
    • Garmin's load focus,
    • your resting-HR baseline and zones.
  • Where a value changed and the change held for two weeks, the tab says since when.
  • Computed from your data every time it is read, never stored, so it cannot go stale.
  • Every coach card and the new MCP tool get_athlete_profile read it.

Ask the coach

  • A question field on the Coach tab: "what am I doing wrong?" becomes a short card with the biggest lever first, its number, and what it means for this week.

Garmin's load focus

  • Garmin's 4-week load per band (low aerobic, high aerobic, anaerobic) against the range it sets for you, with its verdict, for example "aerobic high shortage". It sits on the Trend tab and in get_training_load.
  • It is Garmin's opinion, shown next to the app's own minutes. No rule reads it.

The week's size, found by synthetic athletes

  • A week held on the load ratio is never bigger than the week planned before it, even three holds in a row. Before, an athlete who kept running above plan saw the held week grow.
  • A step is never smaller than the week before.
  • Back from a pause you rebuild: the week grows from your last seven days, with no down week until you are back to 80 % of your old level. Before, a down week mid-rebuild and a lagging median stretched the way back.

Under the hood

  • Garmin account settings (units, language, first weekday) are synced once a day. Nothing else from the account is kept.
  • Migration 0004 adds the load-focus columns.
  • A golden test pins the week the planner builds without habits, over 3,150 combinations, so it stays exactly as before.

Evals: 32/32

  • Three new cases:

    • a learned long-run day is changed by proposing again;
    • Garmin's load focus is a second opinion;
    • an open question gets the biggest lever first, short.

    All three fail without the skill files.

  • A case can now set a word limit that is checked in code (max_words).

Not affiliated with Garmin. A training tool, not medical advice.

Assets 4
Loading