AI training plan
An AI IRONMAN training plan that follows your real week.
A full IRONMAN plan is a block of many months across three sports plus fuel. Ask your own AI to build it, and Memory.fit lets the AI read your swims, rides and runs, your sleep and recovery, and the race you picked. It writes phases, key sessions and a taper into Memory.fit, and the sessions reach your watch.
Memory.fit does not write the plan or tell you what to do. Your AI does, and everything it writes shows in the app with its name.
A block across three sports
Your AI starts with get_workouts, get_training_load and get_athlete: how many hours you train now, how they split across swim, bike and run, and your thresholds. It saves the race with set_race and writes the block with set_training_plan: build phases, a taper, and the weekly rhythm that fits your hours. Sessions are written with plan_session and set_session_structure, and the AI can mark the long ride and long run with set_session_key.
You can tell your AI how many hours you really have, which days are fixed, and where you are weaker. It plans around that.
A full IRONMAN build needs more than a table of workouts: it needs a plan that survives travel, illness and fatigue. Because your AI reads your data each time you ask, it can rebuild the next weeks when life changes, and it keeps the key sessions in place.
- Phases and a taper toward your A race
- Swim, bike and run sessions with steps and targets
- Brick sessions and long days marked as key
Adapting through a long build
Over a long build, weeks go wrong. Ask your AI to check in each week: get_updates shows what arrived, get_session_compliance compares sessions with the plan, and get_sleep and get_daily_metrics show recovery. Your AI can move a long ride with move_session, skip a session with skip_session and lighten the next days. If a connection breaks, your AI can tell you.
Race week matters too. Your AI can write the taper, the race plan with set_race_plan, and a fuel plan for the bike and the run.
Fuel and race day
Long days need a fuel plan. Your AI can write one per session with set_session_fuel_plan, with carbohydrate, fluid and sodium per hour, and practice it in training. Sports nutrition research gives higher carbohydrate ranges for events of several hours (Jeukendrup review), and your own gut training decides what works for you.
Memory.fit has fuel plan pages for IRONMAN races such as Kalmar, Frankfurt, Hamburg and Lanzarote. Open one, or ask your AI to write your race plan with set_race_plan.
Which watches get the sessions
Garmin gets swims, rides, runs and strength with steps. COROS and Wahoo get runs and rides, Suunto gets runs, rides and swims, and intervals.icu gets all four and can pass rides on to Zwift. Recordings come back, so your AI sees each step against its target.
In your AI
The AI you already use, with your data in Memory.fit.
- ChatGPTChatGPT plans your week, fuels your long sessions and writes it all back to Memory.fit.Set up ChatGPT
- ClaudeClaude writes your plans back to Memory.fit, and asks you before it replaces or removes something you have.Set up Claude
Grok BotGrok Bot plans and reviews from your real training, and can re-plan a week after a bad night's sleep.Set up Grok Bot
MuseMuse plans sessions from your real training and writes them into Memory.fit's Plan.Set up Muse
DotsOpenAI says a dot's background research uses your connected apps read only, so plans are written when you ask in the chat.Set up Dots- GeminiType @ in a Gemini chat and pick Memory.fit to ask about your training. Gemini asks you to allow each session it plans, and planning a whole week is not reliable yet.Set up Gemini
- GrokGrok reads your training, sleep and fuel, and can plan around them.Set up Grok
- Perplexity ComputerPerplexity Computer reads your training in Memory.fit. Whether it writes a plan back isn't checked yet.Set up Perplexity Computer
- Claude CodeClaude Code reads your training and writes the sessions it plans back to Memory.fit, asking before each change unless you allowed it.Set up Claude Code
CueYour Cue agents plan your week and write your fuel plans from your real training, sleep and recovery.Set up Cue
What to send
Copy one, send it to your AI.
“Read my last 12 weeks in Memory.fit and plan my IRONMAN build, with phases, key sessions and a taper.”
Tools:
get_workoutsget_training_loadset_training_plan“Add IRONMAN Kalmar as my A race in Memory.fit and plan around 12 hours a week.”
Tools:
set_raceset_training_plan“Plan this week in Memory.fit with a long ride and a brick run, and send both to my Garmin.”
Tools:
plan_sessionset_session_structuresend_session_to_devices“Write a fuel plan in Memory.fit for Saturday's 5 hour ride.”
Tools:
set_session_fuel_planget_session_fueling“Check in on my week in Memory.fit and tell me what to change.”
Tools:
get_updatesget_session_complianceget_sleep
Questions
In short.
Yes. Your own AI, connected to Memory.fit, reads your swim, bike and run data and writes the block into Memory.fit.
No. Memory.fit has no template plans and makes no recommendations. Your AI plans from your data.
Garmin, COROS, Suunto, Wahoo and intervals.icu receive structured sessions. Details differ by sport.
Yes. It writes a fuel plan per session and for race day, and Memory.fit shows it with the session.
Ask it to check in. It reads what you did and how you slept, then changes the next days and says why.
Sources · Checked November 10, 2026
Your next chapter starts with everything you've learned.
On Android now. iPhone is coming: join the waitlist and we'll email you the day Memory.fit is on the App Store.
No spam. One email when it's ready.