An AI fitness coach plans and reviews your training and eating from a record you build by talking to it. In ChatRPE you report a set, a meal, or a short night of sleep, and each one becomes a structured entry the coach reads the next time you ask it something.
Any chatbot can produce a twelve-week program in thirty seconds. What separates a coach from a plan generator is whether Thursday's answer accounts for what you reported on Tuesday, and that is something you can test in a week.
A check-in is two sentences, not a questionnaire
Report what could change today: sleep, soreness, the time you actually have, a meal you want counted. There is no daily form to complete, and leaving something out costs you nothing.
"Slept six hours, legs sore, training at 6 p.m. and I only have half an hour. Adjust today's session but keep the main lift."
ChatRPE revises the session around that and saves the parts worth keeping, the short night and the soreness included, so the next review has them. What you want back is a session you can run. If the reply arrives as encouragement instead, ask for the specific version: "give me the three exercises and the loads."
Starting at all is a different problem from checking in. How to start going to the gym covers the first few visits, and workout motivation looks at why a routine that was working stops.
What the coach already has when you open a chat
Before you type anything, ChatRPE loads a short brief: your profile, your twenty most recent entries, an example of the shape of every data type you track, and a titles-only list of your ten most recent conversations. That is why a returning user gets no reintroduction, and why "same as Tuesday, add five pounds" works as a complete message.
Twenty entries is a window, not your archive. Older history is fetched when a question needs it, filtered by type, period, or keyword, so name what you want: "pull my bench sets from the last three months." A request for a period returns what that query returns rather than a guaranteed complete history, which is worth knowing when you ask about a whole year.
Long conversations are compacted as they run, and earlier chats arrive as titles rather than content. So if you remember settling something in a previous session, say so and the coach can read a summary of that conversation, bounded to its latest turns. "We talked about this a few weeks ago" is enough to send it looking.
Settings holds one more thing worth reading. Your Coach's Notes is a few hundred words on your goals, progress, constraints, and the direction the coach thinks it is working in, generated from your record rather than typed by you. It refreshes on demand and when you open it a day or more after the last version. Correct anything wrong in it by fixing the entry or telling the coach, then refreshing; the workout journal guide covers what ends up in there.
Ask what the record supports
"Is my bench improving" invites reassurance. "Show me my top bench set with RPE for the last eight weeks" invites an answer. ChatRPE charts logged values and can derive an estimated one-rep max from weight and reps. It does not save derived numbers as entries; it computes them when you ask, which is why a bad log corrected today fixes every chart built from it.
An answer about your history should show you what it read. In browser and native chat, ChatRPE is instructed to link the logs behind a claim, so "your top set moved from 185 to 205" arrives with each session it counted as a short link in the sentence. Tapping one opens that entry over the conversation: its saved fields, its date, and any note you attached, with a share button beside the title. A chart can be attached to a phrase the same way and opens in the same card.
The brief loaded before you type carries each of those twenty entries with its identifier, so even the first reply in a new chat can point at a specific session instead of summarizing one. When an answer arrives with no links at all, ask which entries it used before you act on it. Siri replies stay plain text, so this checking happens on screen rather than by voice.
For attendance, ask for the count rather than trusting the impression. A heatmap of logged sessions shows the gaps that a memory of a busy month rounds away. Views you check repeatedly can be saved to a dashboard, covered along with the iPhone widgets in the dashboard guide.
Sleep and nutrition entries add context to a stalled lift, though two lines moving together is an association and not a cause. Three short nights and a missed rep could be one story or two unrelated ones. Ask what the record supports, what is missing from it, and what would be worth logging for two weeks to tell the difference.
The workout log guide covers the detail that makes those comparisons possible at all. For programming decisions, use the workout planner; the guided session guide covers running the plan set by set.
Coming back after a week you missed
Say the plain version rather than an apology: "I trained once in the last two weeks, work was heavy, I'm back Monday with three days free." Ask for the first session, not a schedule that repays the missed ones. Those sessions are gone, and a week built around cramming them back in is harder than the week you just failed to finish.
After a longer layoff, ask for the reduced return on purpose: the same exercises, lighter top sets for the first week, and a review after three sessions. Then log that first session. A logged restart is what lets you read the next gap as a gap, rather than discovering months later that the record simply stops.
A reminder can carry a specific job, as in "remind me at 7 p.m. to log dinner." Pick a time when you can still act on it, and delete the ones you have started swiping away, because those teach you to swipe away the next one too. The habit guide covers tracking the behavior itself.
Separately, with notifications turned on in the iPhone app, a check runs every six hours, reads your recent logs, and writes only when the data gives it a reason. It stays silent otherwise, and it does nothing until you enable it. The accountability guide covers both mechanisms and how to keep them under control.
Test one for a week before you rely on it
A sample program tells you almost nothing, because every model can write one. A week of ordinary use tells you whether the loop closes. Four checks are worth running deliberately:
- Correct something. Log a set wrong, then say "that bench was 175, not 185," and open the cited entry to see whether the saved value changed or only the apology did.
- Ask for history you have not mentioned in this chat, then open two or three of the entries behind the answer and check them against what you actually did.
- Ask why a suggestion was made. Reasoning you cannot interrogate is reasoning you cannot adapt when your week falls apart.
- Act on one suggestion, report how it went, and see whether the next answer knows about it.
Whether you keep using any of this depends on how the logging feels on a bad day. Type it, tap the microphone and speak it, or use Siri on an iPhone without unlocking, covered in the hands-free guide. A meal photo returns an estimate, a barcode lookup returns a database match worth checking against the serving you actually ate, and a lift photo, or a video on Premium, can go in for form feedback.
Chat itself runs in a browser on any device. Siri, push notifications, and home screen widgets come with the iPhone app, so if those are the parts that would keep you honest, that is where they live.
You also do not have to count every gram to get something out of the food side. The nutrition coach guide explains the looser version, and the calorie tracker guide covers when more precision earns its cost. For anything outside the usual categories, such as mood, grip strength, or knee pain, the custom tracking workflow covers defining your own metric.
Keep medical questions with a clinician. Persistent symptoms, medication, pregnancy, or a history of disordered eating call for individual advice, and a log is useful there mainly as a record you can bring to the appointment.
Frequently asked questions
How is an AI fitness coach useful if I already have a program?
Use it to record what you completed and to review the results against the program's own rules. Give ChatRPE the progression rule you are following, then ask whether the recent sets support adding load, adding reps, or repeating the prescription. If the plan came from a general chatbot, the ChatGPT workout plan guide covers moving it onto a record that survives the block.
How often should I check in?
Often enough to capture what you want to use later. Logging each workout is enough for a training review, while questions about nutrition or sleep need entries from those days. A sustainable level of detail beats a thorough one you abandon in week three.
What happens to a long conversation?
It gets compacted as it runs, so the earliest turns reach the coach condensed rather than verbatim. Nothing you logged is affected, because entries are saved separately from the chat. If something from earlier in a long session seems to have dropped out, restate it or ask the coach to look it up rather than assuming it was lost.
How do I know it is not making up my numbers?
Check the links. When ChatRPE refers to past logs in browser or native chat, each one renders as an inline link that opens the saved entry, so a claim about your last three sessions can be read back against the entries it came from. If a summary arrives without them, ask which entries it used.
Can an AI fitness coach replace a personal trainer?
It can handle planning, logging, progression reviews, and reminders. An in-person trainer watches you move and corrects you in the room, which no chat interface does. Decide which of those you actually need; if you use both, the saved record is what makes the trainer's hour more productive.