Feature
Log workouts in plain English.
No forms, no exercise search, no rep counters. Describe the session the way you'd say it out loud and it becomes structured data.
Start for free →14 days free. Card not charged until the trial ends.
Why it matters
Data entry is where logging dies
Nobody stops training because they lost interest in training. They stop logging because logging is a chore performed at the worst possible moment — mid-session, out of breath, holding a phone with one hand.
A form-based tracker asks you to pick a routine, search a database, and fill three fields per set. Every one of those steps is a place to give up. Removing them isn't a convenience feature; it's the difference between a complete training history and a partial one.
How it works
Five spellings, one movement
The quiet way a log goes bad is naming drift. Write "incline DB press" one week and "incline dumbbell press" the next and you end up with two histories, each looking flat, because the sessions are split between them.
What you type is matched against a catalogue of over 500 movements and their aliases, then stored under one canonical name. The same resolution runs on every path into the app — the in-app assistant, MCP, the REST API, and the manual editor — so nothing can sneak a variant spelling in through a side door.
- Abbreviations and shorthand: OHP, RDL, DL, pushdowns
- Singular and plural treated as one movement
- Pounds and kilos, converted on the way in
- Bodyweight, distance, and timed work all supported
- Rename a movement once and every past session follows
Getting it wrong
Corrections are just the next sentence
Any system that parses language will occasionally misread one. What matters is how expensive that is to fix. Here it costs one more sentence: "that squat was 235" updates the set that's already there rather than appending a second one.
When you'd rather do it by hand, every workout opens in a plain editor with each set as a field. The conversational path is the fast one, not the only one.
Things you can type
- Squats 5x5 at 225, leg press 3x12 at 360, lunges 3x10 each leg
- One workout, three exercises, every set parsed.
- 3x10 OHP 95lbs then lateral raises 3x12 at 20
- Shorthand resolved to Overhead Press and Lateral Raise.
- Ran 5k in 24 minutes
- Distance and time, no sets or reps required.
- That squat was actually 235
- Updates the existing set. No duplicate.
- Pull-ups 4x8
- Bodyweight, so no load needed.
Questions
Do I have to use the proper name for an exercise?
No. What you type is resolved against a catalogue of more than 500 movements and their aliases, so "bench", "benching", and "barbell bench press" all land on the same movement. Common shorthand — OHP, RDL, DL — is handled explicitly.
Can I log a whole session in one message?
Yes, and that's the intended way to use it. "Squats 5x5 at 225, leg press 3x12 at 360, lunges 3x10 each leg" creates one workout with three exercises and every set parsed.
What if it gets something wrong?
Say so in the next message — "that squat was 235, not 225" or "it was 5 sets not 3". It corrects the existing entry rather than creating a second one. There's also a manual editor for any workout.
Does it understand kilos and pounds?
Both, in the same sentence if you like. Set a preferred unit in your profile and log in either; the conversion happens on the way in.
What about exercises with no weight?
Bodyweight movements, runs, and timed work all log fine. A pull-up doesn't need a weight and a run doesn't need sets — the log records whichever of weight, distance, duration, and reps the movement actually has.
Does typing it badly matter?
Not much. Abbreviations, slang, and typos are expected. The failure mode is that it asks you what you meant, not that it silently records something wrong.
Type your next session.
There's nothing to set up first.
Create free account →14 days free · card not charged until it ends · cancel in one click
Already have an account? Log in