September 9, 2026
What Does an AI Running Coach Actually Do?
Sunday died at the bike tunnel. The useful coach changes Tuesday, not the paragraph about listening to your body.
Sunday was supposed to be 16 easy. I got as far as the bike tunnel, into a wind that made the easy pace feel like a tempo, and turned around. The calf had been muttering since Friday. I walked the last stretch home with the watch still running, which is a stupid kind of honesty, and then I stood in the kitchen and did the thing I always do: I opened something that calls itself a coach and told it the day had died.
What came back could have been written for a stranger who also owns shoes. Listen to your body. Consistency over perfection. See you Tuesday. The tempo was still sitting there at the same pace, as if the tunnel had not happened.
That paragraph is not coaching. It is a tone of voice.
What I wanted, and what I ended up building, is duller than a chat. I am Rico. I founded Runapt after too many of these kitchen conversations with a box that would not move the week. The missed run stays missed. You do not pay it back on Thursday because the calendar had a hole. The VDOT paces on what is left of the week are allowed to move, because a Sunday that never happened is information, not a debt. Readiness looks at the calf, the sleep, the load you actually banked, and rewrites the rest of the week. The long run does not get stapled onto a recovery day because a box was empty.
That is the whole job, if "AI running coach" is going to mean anything. Not a conversation about running. A next session that is different because this one was.
A chat can still tell you what a tempo is. Plenty of them do it cleanly. They do not know you turned around. They cannot pull Thursday down. If tomorrow is identical no matter what you tell them, you bought a search box with nicer manners. If the plan shifts and nobody will say why, that is the other failure. Silent reshuffles feel clever until you are standing at the door wondering which part of the week just lied to you.
I still override it. Last March the note would have let me run, and I did not, because the left calf had been talking since the train back from Rotterdam. Pain wins. The app does not get a vote on that step. What it does get is the morning after: one clear session before I leave the house. What, how fast, and then I go. Not a menu of ways to make the kilometres back.
If you are comparing labels, ignore the label. Ask what happens to Tuesday when Sunday is a walk. That is the week I would start with, and it is the one I built the first version around.
The other tell is a run that did happen, and happened wrong. You held the pace, and the note afterwards should be allowed to say the day was heavier than the split. A clean average can still be a grind if the wind on the polder did half the work. If the only memory the system keeps is the distance, it will keep printing the same Tuesday. I watched that loop for years, in other apps and in my own log before I built this. The kilometres looked fine. The week did not.
The test is small. Tell it something true and inconvenient. A missed Sunday. A calf. A night that was not sleep. Then look at the next three days, not at the sentence it wrote about you. If those days moved, and you can see why, you have a coach. If they did not, you have company.