Connect your AI assistant to your Garmin watch
Running Workout exposes an MCP server: a standard bridge that lets an AI assistant read your training and write workouts to your Garmin. This guide shows you how to plug it in, whichever assistant you use.
What is an MCP server?
MCP (Model Context Protocol) is an open standard that lets an AI assistant connect to an outside service. Once the connector is added, your assistant gains tools: it can read your activities and create workouts on your Garmin account. You install nothing on your computer — we host the server.
Before you start
One thing to do, the same for all three assistants.
Create your account and connect Garmin
On runningworkout.fr, click “Connect Garmin”. You authorise Running Workout from Garmin Connect: your password is never sent to us, and you can revoke access at any time.
Note the server address
This is the only thing to copy. It is the same for everyone and holds no secret: you sign in afterwards, in your browser.
MCP server address
https://www.runningworkout.fr/mcp
Choose your assistant
Connecting with Claude
On claude.ai, in the desktop app, on mobile or in Cowork, the steps are the same.
Opens claude.ai with the address already filled in (steps 1 and 2 below) — all that's left is to sign in and turn the connector on.
-
1
Open connectors
In Claude, go to “Customize”, then “Connectors”.
-
2
Add a custom connector
Click “Add custom connector”, paste the server address, then confirm with “Add”.
-
3
Sign in
Click “Connect”. Claude sends you to runningworkout.fr: sign in, then approve the authorisation screen listing what the assistant will be able to do.
-
4
Enable the connector in your conversation
In the chat, open the “+” menu and switch on Running Workout. This is the most common oversight: without it, Claude does not see the tools.
In the terminal, with Claude Code
One command is enough, then start authentication with the /mcp command.
claude mcp add --transport http running-workout \
https://www.runningworkout.fr/mcp
Team and Enterprise accounts
The organisation owner first adds the connector from “Organization settings”, “Connectors” tab. Each member then clicks “Connect” from Customize > Connectors, with their own Garmin account.
What your assistant can send to your watch
Running, cycling or pool swimming: here are the targets you can ask for, sport by sport, and how to phrase them in plain language. Some have just been opened up to new sports; others remain specific to one.
infoGood to know
Your assistant writes directly to your Garmin Connect account. It never guesses: it uses the values from your profile (HR max, VMA, FTP, CSS) to turn a percentage into a real value. If one of these values is missing, it tells you and sends nothing to your watch rather than inventing a target — see Your athlete data.
| What you can ask for | Running | Cycling | Swimming | How to say it |
|---|---|---|---|---|
| No target (free pace) | "20 min easy, no target" | |||
| Pace | "3 km at 4:30/km" | |||
| Percentage of VMA | "6 × 800 m at 95% VMA" | |||
| Percentage of HR max | to confirm | "45 min between 70 and 75% of HR max" | ||
| Heart rate in bpm | to confirm | "40 min between 140 and 150 bpm" | ||
| Heart rate zone | to confirm | "1 h in zone 2" | ||
| Power in watts | "3 × 10 min at 220-230 W" | |||
| Power zone | "20 min in power zone 4" | |||
| Cadence | to confirm | "holding 90 rpm" · "at 180 steps/min" | ||
| Swim pace (/100 m) | "8 × 100 m at 1:45/100 m" | |||
| Offset from your CSS | "6 × 200 m at CSS + 3 s" | |||
| Swim effort instruction (1-10) | "4 × 50 m descending" | |||
| Two targets at once Not possible for swimming, for a format reason: the watch only reserves two target slots per step, and the second is already used by the length's primary target (pace, CSS or instruction). | "3 × 8 min at 250 W while holding 90 rpm" |
Structure of a workout
- Five possible intensities for a step: warm-up, active, recovery, rest, cool-down.
- Repeat blocks, nested up to 5 levels deep — for example "3 × (5 × 200 m + 200 m recovery) with 3 min between blocks".
- A step's duration can be given in time, in distance, or left open (the watch's "lap" button).
- A workout can be placed directly on a date in your Garmin calendar.
What your assistant can read
The mirror of writing, and often overlooked:
- the list of your completed activities, with duration, distance, average and max heart rate, pace, cadence, lengths, elevation gain, calories;
- the detail of a completed workout: full summary, normalized power, effective cadence (zeros excluded), moving time, laps (up to 50), and for swimming the length-by-length detail (time, stroke, stroke count, SWOLF) when the file is available;
- your athlete profile and its metrics, with the origin of each value;
- your notes;
- your calendar of planned workouts.
A useful asymmetry to know: activities and notes are read locally, with no Garmin call, so instantly. The calendar and writing workouts, on the other hand, go through Garmin.
Running
Every target in the table above is available. A percentage of VMA is translated into a real pace from YOUR VMA at the time it is sent; if you change it afterwards, workouts already sent do not move.
Cycling
Power is expressed in absolute watts, never as a percentage of FTP.
A step can carry two targets at once — power and cadence, for example.
.zwo export for Zwift
Your cycling workouts can be exported to .zwo format from the calendar, for Zwift and compatible apps. Worth knowing, because it can silently produce a wrong workout: .zwo does not accept watts, only a percentage of a reference FTP. Running Workout uses a fixed reference FTP of 160 W, written into the workout description. This value must match the setting in the app that reads the file, or every target ends up shifted by the same percentage, silently.
Pool swimming
Pool length is mandatory (25 m, 50 m, 25 yd…).
Steps are counted in distance, never in time — except rest steps, which are in seconds.
Stroke, drill and equipment can be specified for each step:
Freestyle · Backstroke · Breaststroke · Butterfly · Individual medley · Choice — Kick · Pull — Paddles · Pull buoy · Fins · Kickboard · Snorkel
A watch quirk worth knowing
When a repeat block ends with a rest step, the watch skips that last rest. If you want a pause before the next set, ask for an explicit rest step after the block.
Limits — stated clearly
| Limit | Wording |
|---|---|
| Calendar | A calendar lookup covers at most 62 days. |
| Activities | At most 100 activities per request. |
| Readable workouts | Only workouts created through Running Workout can be read back in detail; ones built directly in Garmin Connect are invisible to your assistant. |
| Editing | A workout is never edited in place: it is deleted and re-created. There is no "edit" command — that is a deliberate choice, not a temporary limitation. |
| History | Activities from before you connected only exist if you have run an import. |
| Sports | Running, cycling and pool swimming. Not yet strength training, marked trail running, or a full triathlon. |
| Target resolution | A percentage (VMA, HR max) requires the matching value in your profile. If it is missing, the workout is not created, and your assistant explains what to do. |
My assistant tells me it doesn't know my HR max.
That is the intended behaviour: without a declared HR max, no heart-rate-percentage target can be translated into a real value, and your assistant would rather tell you than send a wrong workout. Declare it by giving the number in conversation, or ask directly for a target in bpm, which does not depend on any profile data.
My assistant doesn't see my recent activities.
Activities arrive via Garmin notification, sometimes with a few minutes' delay. History from before you connected requires an explicit import from your dashboard.
The workout is on Garmin Connect but not on my watch.
That is the sync between Garmin Connect and your watch, independent of Running Workout — check that your watch has synced recently (Bluetooth or Wi-Fi).
My assistant can't find a workout I created in Garmin Connect.
Only workouts created through Running Workout can be read back in detail. A workout built by hand in Garmin Connect has no local copy to consult.
How do I remove a workout from my calendar without losing it?
Two different actions: unscheduling removes the date without touching the workout, which stays in your Garmin library; deleting removes the workout itself (and, with it, every scheduled date).
Your athlete data: where your numbers come from
VMA, FTP, CSS, HR max: where these numbers come from, who can change them, how to fix a wrong value, and how to read their history.
The origins of a value
| Origin | What it means | Who writes it |
|---|---|---|
| historycomputed | Estimated automatically, every week, from your activities. | The system |
| verifiedtest | Value computed from an explicitly selected test | You, from the dashboard |
| auto_awesomeAI | Value declared via AI assistant | Your assistant, with your agreement |
| watchGarmin | Value inherited from your Garmin watch | Your watch, automatically |
Priority rule
In this order: a value verified by test always wins; failing that, a value you declared to your assistant; failing that, an automatically computed value; only failing all of those, the value inherited from your watch or entered in Settings. One consequence worth knowing: a value declared to your assistant one day keeps outranking a more recent Garmin import, until you correct it yourself.
Weight, height and a few other fields can also be typed directly into Settings → My profile: they then carry the same "declared" badge as when your assistant records them for you, just through a different door.
Why this mechanism exists
An automatic calculation used to scan every workout without knowing which one was a test. It once produced an FTP of 167 W on a ramp test, where the correct formula gave 194 W: the 20-minute average smoothed out the easy first minutes of the ramp. Since then, VMA, FTP and CSS are no longer estimated in the background: you designate the test workout yourself, and the system applies the correct protocol's formula.
Declaring a test — the three protocols
VMA (running)
| Protocol | When to use it | Formula |
|---|---|---|
| Continuous effort | A half-Cooper or VAMEVAL-style test, on a workout at a steady, sustained effort. | Best rolling average speed over 6 minutes. |
| Progressive test | A step test with increasing stages, to exhaustion. | Best 60-second average, last minute excluded. |
Safety bounds: 8 to 25 km/h. Outside these bounds, the calculation is refused and nothing is recorded.
Prerequisite: the activity must have its detailed data ("GPS available" in the list).
FTP (cycling)
| Protocol | When to use it | Formula |
|---|---|---|
| Steady effort | A classic 20-minute test at constant intensity. | Best average power over 20 minutes × 95%. |
| Ramp | A ramp test (+20 W/min until failure). | Best average over 60 seconds × 75%. |
Bounds: 50 to 600 W.
Prerequisite: a power meter. The system spots ramp tests from the staircase shape of the power curve and pre-selects the right protocol — you confirm it.
CSS (swimming)
Critical swim speed is derived from two efforts at different distances.
| Protocol | What you need |
|---|---|
| Two distances in the same workout (preferred) | A pool workout containing two efforts (for example 200 m then 400 m). The system suggests the laps; you tick exactly two. |
| Two separate workouts (fallback) | Two complete workouts at different distances. |
Formula: CSS = (distance₂ − distance₁) ÷ (duration₂ − duration₁), converted to seconds/100 m. Constraints: distances between 150 and 800 m, a gap of at least 100 m, the longer effort must take more time. Result bounds: 50 to 180 s/100 m.
Consistency between lengths × pool length is also checked, with a 15% tolerance.
From the dashboard
Click the "test tube" icon on a tile, choose the test activity, run the calculation. This is the recommended path: the result is deterministic and traceable back to the source activity.
By talking to your assistant
"I did an FTP test yesterday, 210 W." It records it with the note "test result reported by you".
By correcting a sensor
"My watch counted 1,100 m but I swam 1,000." Recorded with the note "sensor correction confirmed by you".
What your assistant is not allowed to do
Your assistant can never record a value it simply inferred from your profile. It must rely on one of these real events: you reported a test result to it, it spotted a sensor inconsistency you confirmed, or it proposed an update and you said yes. Every recorded value carries which of these three reasons applies, and you can read it back.
HR max, resting HR and VO2max follow a different path: your watch sends them automatically (when it measures them), with nothing for you to ask. You can also type them yourself in Settings if your watch does not report them.
Reading and cleaning your history
Clicking a tile opens the full history of the statistic: every value, its date, its gap from the previous one, its origin, its method and any note.
Declared and test-derived values can be deleted. Computed values cannot: they regenerate at the next recalculation.
Recalculate
Updates the computed values from your current activities.
Recalculate the whole history
Rebuilds every computed value, week by week, up to 2 years back. Use it after a large import or a formula fix. Your tests and declarations are never touched.
The other data
| Field | Where to set it | What it is used for |
|---|---|---|
| First name | Settings → My profile | Personalization |
| Email (optional) | Settings → My profile | Only used to reach you if needed (for example, an incident on your account); never shared with a third party or used for marketing. |
| Sex, age | Settings → My profile | Physiological estimates |
| Weight | Settings → My profile | Required to compute watts/kg |
| Followed sports | Settings → My sports | Filters what the dashboard shows. Data for unchecked sports keeps being computed, it is only hidden. |
| HR max, resting HR, VO2max | Inherited automatically from your Garmin watch (if it measures them), or declared in Settings otherwise | Translate HR percentages into bpm and refine the load calculation. Honest limit worth knowing: VO2max has no recoverable history — only values measured after you connected ever appear, never earlier ones. |
| Language | Header selector | Your assistant writes the name and description of your workouts in this language |
Volume, load and ACWR
- Volume: total training duration over 30 days, all sports combined.
- Load (TRIMP): duration weighted by heart-rate intensity.
- ACWR: ratio between your load over the last 7 days and your average load over the last 42.
| Value | Colour | Reading |
|---|---|---|
| < 0.8 | Load trending down — tapering, or a break | |
| 0.8 – 1.3 | Progression zone | |
| 1.3 – 1.5 | Rising fast, be careful | |
| > 1.5 | Rising too fast, higher injury risk |
⚠ These are training indicators, not medical advice.
Why doesn't the automatic calculation recompute my VMA, FTP or CSS anymore?
Because an automatic scan once got it wrong (see "Why this mechanism exists" above). These three values are now only computed on an activity you designate yourself as a test, with the correct protocol's formula — never in the background.
Check that it works
Ask your assistant these two questions. The first reads your data, the second writes to your watch.
« List my last 3 activities »
You should see your real sessions, with duration, distance and heart rate.
« Create 8x400 m at 95% vVO2max for Thursday »
The workout appears in Garmin Connect and on your watch, scheduled on the right day.
check_circle If both requests work, everything is in place.
If it does not work
My assistant sees no tools, what should I do?
The connector is added but not enabled in the current conversation. In Claude, open the “+” menu in the chat and switch on Running Workout. Also start a new conversation after adding it.
The custom connector option does not appear in ChatGPT
Developer mode is off: Settings → Apps → Advanced settings → Developer mode. Also check your account is paid, as custom connectors are not available on the free plan.
Authorisation fails or loops
Sign in on runningworkout.fr first and check your Garmin account is linked. The authorisation screen needs an active session to know which athlete to attach the assistant to.
How do I remove an assistant’s access?
From your Running Workout dashboard, connected assistants section: each authorisation can be revoked separately, and access is cut immediately.
Ready to try?
Connect your watch, plug in your assistant, and ask for your first workout.
watch Connect Garmin — freeResources
What you need to know to have an AI write your sessions: what the Garmin API allows, what existing MCP servers are worth, and the targets specific to each sport.
Getting started
- Connection guide Step-by-step tutorial to connect the Running Workout MCP server to Claude, ChatGPT or Gemini and run your Garmin training from a conversation. Free.
- The AI Coach, in practice Running Workout teaches Claude how to coach: it reads your Garmin data, asks five questions, builds a 10K plan, pushes it to your watch and adapts it every week.
- How an AI coach works An AI coach works via an MCP connector: it reads your Garmin data, builds your sessions and pushes them to your watch, never inventing a VMA.
- AI coach or human coach? Availability, cost, personalization, form analysis: an honest comparison between AI and human coaching for running training.
Connect Claude, ChatGPT or Gemini
- Add Running Workout to Claude, ChatGPT or Gemini The steps for each assistant: the connector URL, the Garmin authorization, and what you should see at the end.
- Check that the connection works The first questions to ask your assistant to confirm it really reads your Garmin account.
- Connection troubleshooting Missing connector, refused authorization, workout not reaching the watch: the common causes and their fixes.
- MCP servers for Garmin MCP servers connecting AI assistants to Garmin Connect: what they read, what they write, what credentials they ask for. A documented survey.
- Connect an AI to your Garmin data Giving ChatGPT, Claude or Gemini access to your Garmin activities: the available methods, what they are worth, and what they expose.
Training plans
- No-VMA restart plan 6-week restart plan, walk-run to continuous running, no VMA required. Pushed automatically to your Garmin watch.
- 6-week 5K plan 6-week 5K plan tailored to your VMA, 3 or 4 sessions a week. Pushed automatically to your Garmin watch.
- 8-week 10K plan 8-week 10K plan tailored to your VMA, 3 to 5 sessions a week. Pushed automatically to your Garmin watch.
- 10-week half marathon plan 10-week half marathon plan tailored to your VMA, 3 or 4 sessions a week. Pushed automatically to your Garmin watch.
- 12-to-16-week marathon plan 12-to-16-week marathon plan tailored to your VMA, 3 to 7 sessions a week. Pushed automatically to your Garmin watch.
- AI-driven multisport plan Building a running, cycling and swimming plan with an AI: what it does well, what it gets wrong, and how to get sessions onto the watch.
Workouts by sport
- Structured running workouts Intervals, threshold or long runs as structured Garmin workouts: which targets exist, how to choose them, and how to have an AI write them.
- Cycling workouts in watts Building a structured cycling workout on Garmin: power in watts, FTP and zones, what changes indoors, cadence and heart-rate targets.
- Pool swimming workouts Building a structured pool swim on Garmin: pool length, pace zones, CSS offset, stroke, drill and equipment. What the watch accepts.
- Pace, FTP and CSS benchmarks The four benchmarks that calibrate structured workouts: what they measure, how to test them yourself, and how often to redo them.
Prepare a race
- Paris Marathon 2027 Paris Marathon 2027: announced date, new organizer, bib lottery. How to build your preparation with an AI coach.
- Paris Half Marathon 2027 Paris Half Marathon 2027: announced date, new organizer, bib lottery. How to build your preparation with an AI coach.
- Valencia Marathon 2026 Prepare for the 2026 Valencia Marathon, Europe's fastest course: 12-to-16-week preparation calendar, pacing strategy and a plan pushed to your Garmin watch.
- New York City Marathon 2026 Prepare for the 2026 New York City Marathon: bridges, wind, late start and kilometre-by-kilometre pacing strategy, with a 12-to-16-week plan pushed to your Garmin watch.
- Chicago Marathon 2026 Prepare for the 2026 Chicago Marathon: flat record course, handling the lake wind, heat-adapted summer training, 12-to-16-week plan on your Garmin watch.
- Amsterdam Marathon 2026 Prepare for the 2026 Amsterdam Marathon: flat course along the Amstel, 12-to-16-week autumn preparation, pacing strategy and a plan pushed to your Garmin watch.
- Frankfurt Marathon 2026 Prepare for the 2026 Frankfurt Marathon: flat and fast course, ideal July-to-October preparation window, Festhalle finish, plan on your Garmin watch.
- La Rochelle Marathon 2026 Prepare for the 2026 La Rochelle Marathon: flat two-loop course, 12-to-16-week autumn preparation, handling the westerly wind, plan pushed to your Garmin watch.
- Nice-Cannes Marathon 2026 Prepare for the 2026 Nice-Cannes Marathon: point-to-point course facing the sea, Cap d'Antibes bumps, heat and wind, 12-to-16-week plan pushed to your Garmin watch.
- Toulouse Marathon 2026 Prepare for the 2026 Toulouse Marathon: flat course between the Garonne and the Canal du Midi, heat-adapted summer training, pacing strategy, plan on your Garmin watch.
- Rennes Green Marathon 2026 Prepare for the 2026 Rennes Green Marathon: slightly downhill point-to-point route, 12-to-16-week autumn preparation, wind management, plan pushed to your Garmin watch.
- Seville Marathon 2027 Prepare for the 2027 Seville Marathon: Europe's flattest course in February, 12-to-16-week winter preparation through the holidays, plan pushed to your Garmin watch.
- Tokyo Marathon 2027 Prepare for the 2027 Tokyo Marathon: flat course, 12-to-16-week winter preparation, cold and jet-lag management, plan pushed to your Garmin watch.
- Barcelona Marathon 2027 Prepare for the 2027 Barcelona Marathon: rolling course with an initial descent and final climb, 12-to-16-week winter preparation, plan pushed to your Garmin watch.
- London Marathon 2027 Prepare for the 2027 London Marathon: downhill then flat course, 12-to-16-week late-winter preparation, crowd and pace management, plan on your Garmin watch.
- Boston Marathon 2027 Prepare for the 2027 Boston Marathon: qualifying time, initial descents, Newton hills and Heartbreak Hill, 12-to-16-week plan pushed to your Garmin watch.
- Rotterdam Marathon 2027 Prepare for the 2027 Rotterdam Marathon: flat course with the Erasmus Bridge, 12-to-16-week late-winter preparation, pacing strategy, plan pushed to your Garmin watch.
- Nantes Marathon 2027 Prepare for the 2027 Nantes Marathon: rolling course along the Loire and the Erdre, 12-to-16-week late-winter preparation, pacing strategy, plan on your Garmin watch.
- Boulogne-Billancourt Half Marathon 2026 Prepare for the 2026 Boulogne-Billancourt Half Marathon: flat, fast two-loop course, 10-week plan set on your VMA, pacing strategy, sessions on your Garmin watch.
- Valencia Half Marathon 2026 Prepare for the 2026 Valencia Half Marathon, the world's fastest half: 10-week plan set on your VMA, heat-adapted summer training, pacing strategy, sessions on your Garmin watch.
- Lisbon Half Marathon 2027 Prepare for the 2027 Lisbon Half Marathon: start on the 25 de Abril bridge, downhill course along the Tagus, 10-week plan set on your VMA, sessions on your Garmin watch.
- Berlin Half Marathon 2027 Prepare for the 2027 Berlin Half Marathon: flat, wide avenues, 10-week plan set on your VMA, late-winter training, pacing strategy, sessions on your Garmin watch.
Getting better at running
- The 6-minute VMA test The 6-minute VMA test explained: protocol, maximal aerobic speed calculation, when to repeat it, and how your AI coach reads the result from your Garmin activity.
- Threshold pace Threshold pace explained: between 85 and 90% of VMA, how your AI coach calculates it, the plan's 3 × 8 min to 30-minute continuous sessions, and the mistakes to avoid.
- Easy endurance Easy endurance explained: 60 to 70% of VMA, 65 to 75% of max HR, why it builds the base, why your AI coach steers it by heart rate on Garmin.
- The long run The long run explained: the 15% rule, easy-endurance pace, marathon-pace blocks at the end of the run, and what your AI coach checks in your Garmin data.
- Short or long intervals Short intervals (30 s to 2 min at 95-105% of VMA) or long (3 to 6 min at 90-95%): what each develops, how the plan sequences them and how your AI coach reads each repeat on Garmin.
- Hill sessions Hill sessions in running: short, medium and long hills, what each develops, where the plan places them, and how your AI coach sends them to your Garmin watch.
- Training load (ACWR) ACWR explained: ratio between the week's load and the month's, calculated from your Garmin activities, the thresholds your AI coach applies and what it changes in your plan.
- The assimilation week The assimilation week explained: volume cut by 30 to 40%, paces kept, one week in four, and the Garmin signals that make your AI coach bring it forward.
- The pre-race taper The taper explained: three weeks for a marathon, two for a half, ten days for a 10K, reduced volume and kept intensity, a typical final week and misleading sensations.
- Running in strong heat Running in strong heat: the rule of paces reduced by 3 to 5% above 28 °C, heart rate as the target on the watch, timing and route, and how to read summer sessions.
- Running in winter Running in winter: the 5 °C warm-up rule, which sessions to replace below 0 °C, the long run versus ice, and how your AI coach reads your winter runs on Garmin.
- Running cadence Running cadence explained: what the watch measures, why 180 is not a universal target, when to work on it, and how your AI coach reads it in your Garmin activities.
- The warm-up The running warm-up: 10 minutes of jogging and progressive strides, its variants by session and season, what changes before a race, and how it reaches your watch.
- Recovering after a race Recovering after a race: the one-day-per-3-to-4-km rule after a 10K, a half or a marathon, what your AI coach puts on the watch during recovery, and how it restarts the plan.
- Going from 3 to 4 sessions a week Going from 3 to 4 running sessions a week: the three Garmin signals that say you are ready, which session to add, and how your AI coach watches the transition.
- Running your first 10K Running your first 10K: the 30-continuous-minute prerequisite, the 8-week plan at 3 sessions, paces set on your VMA, and the race-day instruction sent to your Garmin watch.
- 10K under 45 minutes Running 10K under 45 minutes: the VMA required (14.8 km/h minimum), the 8-week plan at 4 sessions with threshold and VMA, and the race-day pacing instruction on your Garmin watch.
- Half marathon under 1 h 45 Running a half marathon under 1 h 45: the VMA required (14.2 km/h), threshold up to 30 continuous minutes, the 10-week plan and the race-day pacing instruction on your Garmin watch.
- Marathon under 4 hours Running a marathon under 4 hours: the VMA required (13.2 km/h), base volume, the long run with 45 minutes at marathon pace, and the race-day pacing instruction on your Garmin watch.
- Marathon under 3 h 30 Running a marathon under 3 h 30: VMA of 15.5 km/h, 50 km a week, a 1 h 38 half, the 16-week plan at 5 sessions and the race-day pacing instruction on your Garmin watch.
Tools, watch and analysis
- Reading a plan week How to read a training plan week: each session's name and steps, targets in percent of VMA converted to actual pace, the "why" of each session and what you can change.
- Missed session: what to do A missed session in your plan: what your AI coach decides depending on whether it was an easy run, a quality session or a long run, why it never compresses two sessions, and how to prevent rather than make up.
- Moving the race date Moving a race date in your plan: what your AI coach adjusts when the race is postponed or brought forward, the minimum taper it protects, and when it prefers to start a fresh plan.
- Choosing your plan variant Choosing your training plan variant, from 3 to 7 sessions a week: what each variant contains, how your AI coach recommends it from your last 30 Garmin days, and when to change.
- Pace zones on the watch The pace and HR ranges your AI coach sends to the Garmin watch: calculated from your actual VMA, different from Garmin's default zones, how to read alerts while running and when they change.
- Creating a workout in one sentence Creating a structured Garmin workout through conversation: what your AI assistant builds from one sentence, targets converted from your VMA, what it asks when an element is missing, and what it refuses.
- Analysing an activity How your AI coach analyses a Garmin activity: first kilometre, second half, evenness for a race; pace and HR per block for a session; and the numbers it deliberately ignores.
- Cardiac drift Cardiac drift explained: calculation over the two halves of a long run, the 5 and 10% thresholds, what it says about pace and hydration, and what your AI coach changes when it is too high.
- Claude, ChatGPT or Gemini? Honest comparison of Claude, ChatGPT and Gemini for running coaching with Running Workout: what is identical (tools, rules, data), what changes (installation, confirmations, links), and which to choose.
- Useful phrases for your coach Twenty useful phrases to drive your AI running coach: start coaching, run the weekly review, push the week to the watch, create or move a workout, move the race date.
Data and technical
- The athlete data the coach reads VMA, max heart rate, training load: where these values come from, how to check and correct them.
- What the connector can do, and its limits The list of actions available through conversation — create, schedule, move, analyze — and the limits Garmin imposes.
- Writing a workout to Garmin via API The three ways to send a structured workout to Garmin Connect: the official Training API, a FIT file, or a third-party bridge. What each allows.
- The FIT file explained What a Garmin FIT file contains, what it adds over the activity summary, and the cases where you actually need it.