Fix a set you logged wrong

Twenty minutes after the session, you check the summary and realize — the third bench set was 10, not 8. Or maybe it was the day before. Either way, the number on the card isn't the number you actually did. You don't open a form, you just say what's off.

What the agent needs to hear

Behind your sentence, the agent works backwards to three pieces: which set you mean, what’s wrong with it, and the right value. The first piece is the trickiest — you have to point clearly at one set among the many you’ve logged. The other two follow naturally once the agent locks the target.

You can point at a set by position (« the third bench set today »), by content (« the bench set where I put 80 kg for 10 »), or by context (« the last one I logged »). The agent reads your sentence, finds the matching log, and shows you a card with the set isolated and the change highlighted before applying. If nothing matches — or several sets match — the agent will ask one clarifying question before touching anything.

Pointing at the right set

Day matters. By default, the agent assumes today unless you say otherwise. « The third bench set » without a date means today’s third bench set; « yesterday’s first squat set » or « last Monday’s pull session, first lat pulldown » walks the lookup further back. Be as specific as the ambiguity demands — vague pointing on a busy session is what makes the agent ask back.

For sets that are part of a cluster (rest-pause, drop set, superset, pyramid, giant), be doubly specific. « The middle mini-set of the rest-pause on bench today » lands on one mini-set inside one cluster. « The first round of the curls in today’s superset » lands on round one of the curls column. The agent reads the cluster shape and finds the cell.

What you can change

You can change reps, weight, RPE, notes, the exercise the set is attached to, and the set type (« that wasn’t a regular set, it was an AMRAP »). What you usually can’t is move a set across sessions — sets belong to the session they were logged in, and moving them is rare enough that the agent confirms twice before doing it.

If the right move is deletion instead of edit — the whole set never happened, you tapped wrong, you logged the same set twice — say so plainly: « delete the duplicate bench set from today ». The agent confirms once, then removes it.

When the agent gets it wrong

The card the agent shows you before applying the fix is the chokepoint. If it found the wrong set (the second bench set instead of the third), say so: « no, the next one — third set, the one at 80 ». The card re-renders on the correct set.

If the agent isolated the right set but is about to change the wrong field (you said « 10 », the agent thinks you mean weight and you meant reps), call the field: « 10 reps, not 10 kg ». And if the agent matched multiple sets and asks which one, point with the most distinguishing piece: weight, exercise position, or « the most recent ».

What makes the correction worth doing

Three things decide whether the correction lands cleanly: the pointer is unambiguous (so the agent edits exactly one set, not all matching ones), the new value is the truth (not a rounded or aspirational number — what actually happened), and the change applies only to the field you meant (reps or weight or exercise, not all three by accident). The system reads corrected sets the same way as originals — the PR ledger, exercise progression, and weekly volume all re-read from the new value — so a clean fix restores the signal, while a sloppy fix corrupts it twice over. Say what’s off, point at the one set, and confirm the card.