AI training plan
An AI half marathon plan that starts from your last runs.
A half marathon plan should start from the running you do now, not from a table. Connect your watch to Memory.fit, add Memory.fit to the AI you already use, and ask it to plan toward your race. Your AI reads your recent runs and recovery, writes the block into Memory.fit, and each session arrives on your watch.
Memory.fit holds the data and the memory. It does not write the plan. Your AI does, and its name is on every session in the app.
From your runs to a block
Your AI looks at get_workouts and get_training_load to see your current weekly running, long run and pace. It saves the race with set_race, then writes the block with set_training_plan. A half marathon block can be short, so the AI builds backward from the race date, with a taper before it.
Sessions such as tempo runs, intervals and the long run are written with plan_session and set_session_structure, with targets taken from your thresholds in Memory.fit. You can ask it to use heart rate, pace or both.
Training for your first half marathon and for your fifth are different jobs. Tell your AI which one it is, and how many days a week you can run. It can read your history and choose a block that fits, then lower the load if your sleep drops. If you already race often, it can build speed work around tempo runs.
- Race and target time, saved to Memory.fit
- A block with a taper, written by your AI
- Tempo, interval and long run steps in your own zones
Week by week
Ask your AI to check in after each run or once a week. It reads new recordings with get_updates, compares them with the plan with get_session_compliance, and looks at sleep and HRV. If you skipped a run, skip_session records it and the plan adapts. If a hard week left you flat, your AI can lower the next days and says why.
Nothing here locks you in. If the race date moves, ask your AI to move the block.
Fuel and race day
A half marathon often needs little fuel for most runners, and what you take is personal. Your AI can write a fuel plan for a long run or the race with set_session_fuel_plan, using what you told it about your gut and sweat. Sports nutrition guidelines give higher carbohydrate ranges as the effort gets longer (ACSM position stand).
Memory.fit has race pages with a prefilled fuel planner for half marathons such as Valencia, Berlin and Lisbon.
Your watch
Runs go to Garmin, COROS, Suunto and Wahoo, and to intervals.icu, with every step and target. Recordings come back to Memory.fit, so your AI sees what you actually did.
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 recent runs in Memory.fit and plan a 10 week block toward my half marathon, with a taper.”
Tools:
get_workoutsset_raceset_training_plan“Plan this week in Memory.fit with one tempo run, one interval run and a long run, and send them to my watch.”
Tools:
plan_sessionset_session_structuresend_session_to_devices“Compare last week's runs with the plan in Memory.fit and tell me what to change.”
Tools:
get_updatesget_session_compliance“I skipped Tuesday's run. Update my week in Memory.fit.”
Tools:
skip_sessionmove_session“Write a fuel plan in Memory.fit for race day, using my sweat and gut notes.”
Tools:
set_session_fuel_planget_memory
Questions
In short.
Yes. Your AI reads your runs through Memory.fit and writes the plan back, then Memory.fit sends each run to your watch.
Your AI decides from the weeks until your race and the running you do now. Tell it how much time you have.
Any AI that supports MCP connectors, such as ChatGPT, Claude, Grok Bot, Muse, Dots, Gemini or Perplexity.
Yes. Structured runs go to Garmin, and also to COROS, Suunto, Wahoo and intervals.icu.
No. Memory.fit recommends nothing. The plan is your AI's, and you can ask it to change anything.
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.