At some point last winter, half of cycling Twitter quietly started asking ChatGPT to coach them.
Nobody announced it. There was no launch, no app icon, no onboarding flow. People just opened a chat window, pasted in their FTP, and started typing questions they used to ask a forum.
It works better than it has any right to. It also breaks in ways that are completely predictable once you know what to look for.
This is not a takedown. ChatGPT is a genuinely good tool for parts of this job. It’s just not the whole job, and knowing exactly where the line sits is worth more than either loving it or dismissing it.
What it’s actually good at
Ask ChatGPT to build you a training plan and it will produce something reasonable. Progressive overload, a taper before your event, a sensible mix of zones. It has effectively read every cycling training book ever digitised, so the bones of the plan are usually sound.
It’s also a genuinely great study partner. Ask it to explain the difference between sweet spot and threshold work, or why cadence matters on climbs, or what actually happens physiologically when you bonk, and you’ll get a clear answer faster than you’d find one on a forum, and without anyone telling you you’re holding your bars wrong.
Here are the prompts that actually earn their keep.
“Explain [concept] like I already understand training zones but not the physiology behind them.” This is the single best use of a general chatbot for cycling. It’s patient in a way no group chat is, it never gets tired of the question, and it will happily go three levels deeper if you ask “why” again.
“Here’s my FTP and my event date. Build me an 8-week base block with a rough weekly structure.” A completely fair use of the tool. You’ll get a sane skeleton. Progressive volume, one or two quality sessions a week, a down week before it gets silly.
“I felt X during yesterday’s session — what does that usually mean?” Genuinely useful as a sounding board. You describe the sensation, it reasons through the plausible explanations. It won’t know which one is actually true for you, but it’s a decent first pass before you spiral into a 2am forum rabbit hole about whether your legs are broken forever.
“Play devil’s advocate on this plan — what’s the weakest part of it?” This is the prompt most people don’t think to use, and it’s the best one on the list. Ask ChatGPT to argue against its own plan and it will, usually correctly, flag things like “this taper is too aggressive” or “you’ve got back-to-back hard days with no recovery between them.” It’s a genuinely good second opinion, precisely because it has no ego about the plan it just wrote.
Used this way, ChatGPT is a smart, patient, occasionally over-confident training encyclopedia sitting in your pocket for free. That’s a real upgrade over nothing, and it’s worth saying plainly instead of undermining it in the next paragraph.
Where it quietly stops being a coach
Here’s the part that doesn’t fit neatly into a “10 ChatGPT Prompts for Cyclists” listicle, because admitting the limits doesn’t get clicks.
It has no idea what actually happened to you. You can tell it “I missed Tuesday’s intervals,” and it will happily reshuffle the week. But it doesn’t know if you missed them because you were sick, because a meeting ran long, or because your legs were still cooked from Sunday’s group ride. It only knows what you type, in that exact conversation. Open a new chat next week and it has forgotten your FTP, your event, your knee that’s been niggling for a month, and the fact that you already told it all of this once.
It can’t see your data. No power file. No heart rate. No sleep, no HRV, no actual training load — just whatever you happen to describe in a sentence. It will still answer with total confidence, because that’s what it does, but it’s coaching blind and sounding sure about it.
One rider, in Streeka’s own userchat with a coach that does have their data, asked exactly the right question of the tool in front of them:
“Based only on my training data, what can you confidently tell me about my training? What can you only guess? What important coaching context is missing?”
Ask a general chatbot that same question and it can’t really answer it, because there’s no training data behind the conversation to be confident or uncertain about. It’s estimating from a handful of sentences the whole time, and it rarely says so.
Structure without memory becomes a chore, fast. Riders on r/TrainerRoad — a community that already lives inside algorithmic coaching and talks about it constantly — describe the exact shape of this problem, just with a paid product instead of a free one:
“I feel like adaptive training penalizes you for a bad day or missed day, instead of the regular plan keeping you on track.”
A general chatbot has the same failure mode with none of the guardrails. Tell it your week went sideways and it will happily rewrite the whole plan from your description alone, with no sense of what “normal” looks like for you, because it has never seen what normal looks like for you.
You become the memory. This is the one that actually erodes people over time. Every conversation starts from zero, so you become responsible for re-explaining your FTP, your goal race, your niggling knee, your last three weeks of training, every single time you open a new chat. That’s not coaching. That’s data entry with extra steps, and it’s the specific kind of admin that makes people quietly stop using the tool a few weeks in, not because it gave bad advice, but because typing the same paragraph every Sunday night gets old.
The trust question, asked plainly
There’s a thread that shows up constantly across r/TrainerRoad and r/Velo, in almost identical wording each time, whether the coach behind it is free or paid:
“Should I just trust the AI no matter what?”
That’s the actual question underneath all the prompting. Not “is this a good workout” — most AI-generated workouts are fine. The real question is whether you can hand over the decisions and stop relitigating them yourself.
With a general chatbot, the honest answer is: trust it for explaining things, be a lot more careful trusting it to run your season.
One rider summed up the deeper discomfort with algorithmic coaching in general, describing a paid platform, but the sentiment lands just as hard on a free chatbot doing the same job:
“It’s honestly quite dispiriting to think that I might be committing hundreds of dollars a month to someone who is just using AI tools rather than their own personality/knowledge to provide what I need.”
Nobody’s paying ChatGPT hundreds of dollars a month to coach them. But the underlying wedge is the same one that shows up in every thread about trusting AI coaching, free or otherwise: the moment a plan starts feeling like a template rather than something that actually knows you, the trust goes with it, even if the workouts themselves are perfectly reasonable.
The two-minute test
If you want to know exactly which side of the line your ChatGPT setup falls on, don’t ask it a training question. Ask it a memory question.
Open a brand new chat and type: “What’s my FTP, and what did I do last week?”
If it asks you to remind it, you’ve built yourself a workout library with a very polite chat interface. Genuinely useful. Not coaching you — you’re coaching it, every single session.
Most people fail this test the first time they try it, and that’s fine to know going in. It just means the plan stays yours to manage, start to finish, which is a real time cost most people underestimate until they’re three months in and tired of it.
Fixing it without abandoning the free tool
A few things narrow the gap, if you want to keep using ChatGPT as part of your setup rather than replace it outright.
Keep one long-running conversation instead of starting fresh each time, so at least some context survives between sessions. It’s clumsy and it’ll still forget things, but it beats zero memory.
Paste in a short weekly summary rather than relying on it to remember — your total hours, how the hard sessions felt, anything unusual. You’re manually doing the job a system with actual memory would do for you, but at least you’re doing it deliberately instead of accidentally.
Use the “play devil’s advocate” prompt on any plan it gives you before you commit to a week of it. It’s the cheapest sanity check available and most people never think to ask for it.
And be honest with yourself about the test above. If you’re re-explaining your context every time, that’s not a flaw in your prompting. It’s a structural limit of a tool with no memory of you, and no prompt fixes that.
What this is really about
Nobody wants a chatbot for its own sake. Nobody’s actual goal is “have an AI conversation about cycling.”
What people are actually chasing, whether they’d phrase it this way or not, is the feeling of knowing they’re doing the right work and that it’s moving them forward — without needing to relitigate every decision in the shower afterwards.
ChatGPT gets you partway there. It’s excellent at answering the question in front of you. It’s structurally unable to remember the six weeks of context that question actually depends on, because that’s not the job it was built for.
That’s the real gap, and it’s not really about intelligence. It’s about memory and data — the two things a general-purpose chatbot was never going to have, no matter how good the prompt is. Streeka exists specifically to close that gap: it reads your actual rides off Garmin or Wahoo, remembers last week and the six before it, and tells you plainly what it knows versus what it’s guessing, instead of asking you to hold all of that in your head — or retype it every Sunday night.
Use ChatGPT for what it’s genuinely good at. Just go in knowing which parts of the job it was never going to be able to do.