Paces, thresholds and PBs
Remember your threshold pace, FTP, heart-rate numbers and PBs with the date each value became current.
- Threshold pace
- FTP
- Max HR
- 5 km PB
- 10 km PB
- Half marathon PB
Athmex stores the things that matter most like your current thresholds, PBs, goals, races, injuries and equipment as structured, dated facts. Your AI reads them at the start of a conversation, so it has a proper view of you to reason from instead of a guess.
What does my training say about my half marathon next month? I have an hour now, what's the best session I can do?
Your 19:30 5km PB, 4:05/km threshold pace and race in 32 days put that target within reach. One more sustained half-marathon-pace session would strengthen the picture.
Keep it controlled. Finish feeling as though you could complete one more repetition.
ChatGPT and Claude can be incredible for running, cycling, swimming and triathlon to help with everything from setting your next session to training and race plans; but a new conversation doesn’t start with a reliable, proper view of you as an athlete.
If a training factor changes as your season or plan progresses, tell Claude or ChatGPT and ask it to update Athmex. Athmex locks it in and it's then used in your next conversation with AI to keep your training on point.
I'm a triathlete in Belfast. I built Athmex because Claude kept quoting PBs I'd already beaten and injuries I'd recovered from, and every session review started with ten minutes of screenshots, clarifications and reminding it who I was and key context it had forgotten.
The AI training model wasn't the problem. The record-keeping was. The training plans that Claude and ChatGPT made for me have delivered significant performance gains and now the hassle to get there is gone. Read the full story →
It might remember that you mentioned a 5K PB and log that to its own stored memory. The problem is it has no way to tell whether that PB is still current.
It doesn't know whether your threshold has moved since, or whether the hamstring you mentioned in January is still an issue. Athmex stores every value with the date it became current and the date it was superseded. When your FTP or PB changes, the old number is retired, not blended into a guess.
Illustrative example. Athmex keeps the retired value and the date it changed.
A new chat with Claude or ChatGPT doesn't start with reliable context about you as an athlete, and what it does remember can be inconsistent from one conversation to the next. Athmex keeps that context ready, so Claude and ChatGPT reason from your actual numbers instead of guessing.
Remember your threshold pace, FTP, heart-rate numbers and PBs with the date each value became current.
Keep your upcoming races, results, training priorities, recurring injuries, equipment and preferences in the conversation from the start.
Give me a training plan for this week.
Happy to help! A few questions first: what distance are you targeting, what's your current weekly mileage, do you have a goal time or race date, and any injuries I should know about?
| Tue | Threshold | 3 × 8 min @ 4:05–4:10 |
|---|---|---|
| Thu | Easy | 40 min conversational |
| Sat | Race pace | 5 × 1 km @ 3:57, 90s jog |
| Sun | Long | 1h10 easy |
Built for your sub-40 attempt at Laganside in 32 days. You need 3:59/km and your current threshold is 4:05/km, so Saturday is the session that matters most this week.
Two quality running days rather than your usual three. I know your left hamstring eases with lower run volume so let’s make it quality over quantity for a while.
Does that work or do you want me to factor anything else in?
Same prompt, same model. The difference is your Athmex profile.
Add the paces, PBs, goals, races, injuries, equipment, training preferences and more that make your AI truly understand who you are, so you are not pasting the same details into every new conversation.
Your profile is ready whenever you start a new conversation, without pasting anything in first.
Ask about your week, your next race or how to adapt a session without re-explaining who you are.
Already on Strava or COROS? Setup connects that too, at no extra cost.
Athmex holds your athlete profile, not your training feed. It imports no activities, runs no background sync and keeps no second copy of training data held elsewhere.
If you also want an assistant to see recent sessions, connect a supported training platform separately. COROS connects directly to both Claude and ChatGPT; Strava currently connects to Claude. Add an Athmex profile and you'll be prompted to connect Strava or COROS in the same setup, so it's one thing to do, not two.
See pricing for what happens when the beta ends. You'll get plenty of notice first, and nothing is ever charged automatically.
Athmex is free during the open beta with no payment details required. See the pricing page for what happens when the beta ends. You will get plenty of notice, and nothing is ever charged automatically.
Athmex stores the context you choose to provide. Claude or ChatGPT uses it to produce the advice. An activity connector is optional if you also want recent sessions in the same conversation.
No. Athmex stores only the context you give it, such as PBs, thresholds, goals, races, injuries and equipment. It does not import activities or sync data from Garmin, Strava, COROS, Apple or another platform.
If you connect a supported activity source, that source talks to Claude or ChatGPT separately. Athmex never receives the activity feed.
They do different jobs. A watch connector shows your AI what you did last week. Athmex tells it who you are with things like current thresholds, target races, injury history, equipment which is the context that makes last week's data mean anything. Use Athmex on its own, or alongside a connector.
Keep your paces, PBs, goals, injuries and preferences ready in every new chat.