Log a regular working set

You racked the bar after a clean set — the chalk's still on your palms, the bar's still cold from your grip, and you want to log it before the rest timer winds down. No notes, no fuss, just the set.

What the agent needs to hear

Native voice has a narrower set-logging flow. During the limited rollout, recording regular sets requires a workout already attached to the call and set logging enabled for your account. Say “Bench press, 10 reps at 80 kilograms.” A freshly dictated set can be saved without a separate confirmation; check the result before repeating it. If a possible duplicate is detected, the agent asks whether you mean another identical set. Without set logging, use the app. Advanced sets are not supported in Native voice. The card above illustrates an MCP client, not a Native approval step. See the voice guide.

Behind your sentence, the agent works backwards to three pieces: which exercise, the weight, and the rep count. You don’t have to spell every one out — the active exercise in your session is the assumed target, so « 10 at 80 » is enough if you’re mid-bench. If you’ve moved on or you’re between exercises, name it: « 10 at 80 on bench », and the agent attaches the log to the right line.

Order is flexible, but explicit units remove ambiguity: « 10 reps at 80 kilograms ». The larger number is not necessarily the weight. If the exercise, reps or load is unclear, clarify it rather than relying on a guess. For bodyweight work, say that explicitly and name any added load.

Numbers and units

Numbers always override defaults. If you weighted the bar at 82.5, say 82.5 — the unit sticks and decimals carry. Pounds vs kilos: name the unit if it’s not your default; otherwise the agent uses what you set in profile. For « a plate per side », specify the total load including the bar; plate and bar weights vary. For bodyweight work, name the added load separately.

For reps, the convention is what you did, not what was planned. If the program said 8 and you got 10, log 10. If the program said 8 and you cut at 6, log 6. The agent does not coach you about the gap — it logs the truth.

What this signal is for

The working set is the bedrock log. Your PR ledger reads from these — heaviest sets become your one-rep estimates. Volume totals come from these. Exercise progression, weekly review, training quality score, all of it. A clean working set in the right exercise builds the signal; a wrong one corrupts that exercise’s history quietly until you correct it.

Review the saved exercise, reps and weight in your session. An MCP client may show a card; Native voice reports the saved result without a separate approval card.

When the agent gets it wrong

Review the saved result in your session or the MCP client card for what does not match what you actually did. If the rep count is off, say the right one: « it was 12, not 10 ». If the weight got attached to the wrong exercise — you said « 80 for 10 » mid-rest from bench but the session had already auto-advanced to incline — name the exercise: « that was the last bench set, not the incline ».

If your phrasing got read in the wrong direction — rare, but possible at extreme rep ranges — call it: « 20 reps at 60, not the other way around ». Check the corrected value in your session before logging another set.

What makes the log worth keeping

Three things decide whether this set helps you later: the exercise is the right one (so PR ledger and progression stay honest), the weight is what was on the bar (decimals and added load count), and the rep count is what you did, not what was planned (the system reads truth, not intent). The system uses these for the PR ledger, working volume, and exercise progression; a wrong exercise or invented number quietly corrupts an entire lift’s history. Say the set the way you hit it, check the saved exercise, reps and weight.