The coach sees your workout history, your stated goal, your reference pace, and your load trend. It does not see your sleep last night, the soreness in your back, the argument that kept you up, the chest cold you mentioned in chat but did not quantify, or the fact that you skipped breakfast. Some of those you can put into chat — and the coach will use the words you give it. Some of those it cannot read at all: it does not have access to a heart-rate monitor, a sleep tracker, a wearable, or a calendar. That boundary is deliberate, and it is why the product asks you to use words. When in doubt, the coach picks the conservative session. If you have not told it that you slept four hours, it cannot know that you did. The article is an honest map of what is in the model and what is in your court.
Key points
- The coach reads your history, your goal, your reference pace, and your load trend — nothing else by default.
- Sleep, soreness, illness, and life stress are inputs you provide in chat; the coach cannot infer them silently.
- Heart rate, sleep, and wearable data are not read automatically; you choose what to surface in chat.
- When the boundary is unclear, the coach picks the conservative session and asks for more context.
- Tell the coach what you have not told it yet — that is the single highest-leverage habit for safer output.
Sources and further reading
- NHS — Sleep and Tiredness— Reference for sleep's effect on training response, used to set conservative defaults when sleep is poor.
- Cleveland Clinic — Delayed Onset Muscle Soreness— Reference for the time course of muscle soreness and how it changes what the coach should prescribe.
- Mayo Clinic — Exercise and Immunity— Reference for the relationship between training load and immune response, used as a conservative signal.