AI Running Coach: Using Claude and ChatGPT for 5K to Marathon Plans
An AI running coach can build VDOT-based, periodized plans from 5K to marathon. Here is how to brief Claude or ChatGPT, the mistakes to avoid, and how to get the plan onto your watch.
Ask Claude or ChatGPT for a marathon plan and you'll get something that looks remarkably like what a coach charging $200 a month would write: easy mileage, a weekly long run, quality sessions at the right paces, a cutback every few weeks, and a taper. AI has read every running book ever written. Used well, an AI running coach can take you from couch to 5K or from a 3:30 marathon to a 3:15 — for a few dollars a month. Here's how to get the most out of it, and where the limits are.
What Makes an AI Running Coach Worth Using
Running is a pace-and-volume sport, and AI handles both well when you give it the right inputs:
- Pace-based prescription. Give it a recent race or time trial and AI can derive your training paces — easy, marathon, threshold, interval, repetition — using VDOT-style logic. If you haven't got your number yet, our VDOT calculator guide sorts it out.
- The right easy/hard balance. A good plan keeps ~80% of running easy and reserves quality for two or three sessions a week.
- Sensible long-run progression. Build the long run gradually and cut it back on down weeks instead of marching it up every Sunday.
- Race-specific work. 5K plans sharpen VO2 max; marathon plans rehearse goal pace and fueling on long runs.
A strong brief is everything. Try this:
Prompt (Claude or ChatGPT):
"Act as my running coach. Build a 16-week marathon plan for
a 3:30 goal. Current fitness: recent 5K 22:30, running 40km/
week across 5 runs, longest run 20km. Available 6 days/week,
max 75 min on weekdays, long run Sundays. History of mild
calf issues - keep easy days truly easy.
Use VDOT-based paces, ~80/20 easy-to-hard, a cutback week
every 4th week, and a 2-week taper. Give each workout a
specific structure with pace targets."The Mistakes AI Makes (and How to Prevent Them)
AI running plans fail in predictable ways. Steer around them:
- Too much, too soon. A blank prompt will happily jump your mileage 30%. Always tell it your current weekly volume and longest recent run, and ask it to cap weekly increases at ~10%.
- Ignoring injury risk. If you've had niggles, say so. Ask for the easy days to stay conversational and for strength or cross-training instead of a junk-mileage day.
- No memory of your week. A chatbot doesn't know you ran a hilly trail race Saturday unless you tell it. Feed it last week before asking for next week.
The fix for all three is context — which is precisely what a history-aware coach gives you automatically (more on that below).
Getting the Plan Onto Your Watch
A plan stuck in a chat window won't run itself. Ask the AI to export it:
"Output the plan as CSV with columns: day,sport,subtype,
title,duration_minutes,tss,description,phase. Put the
warmup, intervals, paces, and cooldown in description."Take that CSV to TrainingDojo's importer, connect TrainingPeaks or Intervals.icu, set your start date, and the whole block lands on your calendar — which then syncs to your Garmin, Coros, or Apple Watch. For step-by-step workouts your watch counts down for you, convert the runs into structured workouts with pace or heart-rate targets, or bulk-convert the whole plan at once.
Specific race in mind? We have dedicated guides for 5K and 10K, the half marathon, and the marathon.
The Upgrade: A Running Coach That Reads Your History
The recurring weakness of DIY AI coaching is that it only knows what you paste. TrainingDojo's Coach Dojo removes that limit: it connects to your Strava, TrainingPeaks, or Intervals.icu history and reads your last ~90 days of running before it plans a thing.
- It sees your real weekly mileage, longest runs, consistency, and how much quality you've been handling.
- It asks about your goal race, current fatigue, and any injury history — the context Strava can't show.
- It builds a progression that fits where you actually are, then hands you a plan ready to import or structure.
That's the difference between a plan built on a number you half-remember and one built on what you've truly been running. See how Coach Dojo personalizes plans from real data, or use your Strava history with Claude if you prefer to drive the conversation yourself.
The Bottom Line
An AI running coach is genuinely capable: feed Claude or ChatGPT your paces, volume, and constraints and it writes a smart, periodized plan. The two things to get right are grounding it in your real history and getting the plan onto your watch without manual entry. Coach Dojo handles both; TrainingDojo imports any AI plan you bring. Either way, you train instead of typing.
Cyclist too? Here's the companion guide on the AI cycling coach, and our head-to-head on Claude vs ChatGPT for training plans.
Frequently Asked Questions
What is an AI running coach?
An AI running coach uses a model like Claude or ChatGPT (or a tool such as Coach Dojo) to build pace-based, periodized running plans from your recent races, weekly volume, and goal — covering everything from 5K to the marathon.
How good are AI running plans?
Surprisingly good when briefed well. Give the AI a recent race for VDOT-based paces, your current weekly mileage and longest run, your available days, and any injury history, and it will produce a sensible ~80/20 easy-hard plan with cutback weeks and a taper.
What mistakes do AI running plans make?
Without context they tend to ramp mileage too fast, ignore injury risk, and forget what you did last week. Prevent this by stating your current volume, asking for ~10% weekly increases, flagging niggles, and pasting recent training before asking for the next block.
How do I get an AI running plan onto my Garmin or Coros?
Ask the AI for CSV, import it with TrainingDojo to TrainingPeaks or Intervals.icu, and your calendar syncs to your watch. For step-by-step workouts, convert the runs into structured workouts with pace or heart-rate targets.
Why use Coach Dojo instead of a chatbot?
Coach Dojo reads your last ~90 days of running from Strava, TrainingPeaks, or Intervals.icu, so it builds from your real mileage and durability rather than a number you half-remember, and it returns a plan ready to import.