Fix a meal log you got wrong

You logged lunch in a rush — chicken, rice, salad — and noticed afterwards that the chicken was actually 250 g, not the 180 g default the agent assumed. Or maybe the rice was cooked, not raw, which changes the macros. Either way, the day's totals are off until you correct it.

What the agent needs to hear

Behind your sentence, the agent works backwards to three pieces: which meal log, which entry inside it, and what to change. Naming the meal type (lunch, dinner, snack) is usually enough on a normal day; the agent reads « lunch » as today’s lunch by default. If the meal is from another day, say so: « yesterday’s lunch chicken » or « last Tuesday’s dinner rice ».

For the entry inside the meal, you can point by food name (« the chicken »), by position (« the second item »), or by content (« the 180 g chicken »). The agent reads your sentence, finds the matching entry, and shows you a card with the entry isolated and the change highlighted before applying.

What you can change

Quantity is the most common edit — you weighed something after logging and the number was off. « 250 g, not 180 » updates the chicken’s quantity and refreshes the meal’s macros on the spot. Unit changes work the same: « 200 g cooked, not 200 g raw » changes the unit and the agent rolls the macro math accordingly.

You can also change the food itself if you logged the wrong item (« that was brown rice, not white ») or delete an entry entirely if it never happened (« remove the salad — I didn’t actually have it »). The meal type can change too — « that was a snack, not lunch » moves the whole log to a different meal slot. The day stays consistent across the change.

When the meal is missing entirely

If you forgot to log a meal and want to add it after the fact, that’s not a correction — it’s a new log. The agent treats it the same as a fresh meal log but with an explicit date: « add a snack for 3 pm yesterday — handful of almonds, glass of water ». The new log slots into the day and the daily totals re-compute.

If you logged a meal at the wrong time of day (you logged « breakfast » at noon for a meal you ate at 7 am), correcting the time is a single-field edit on the existing log, not a delete-and-re-log: « breakfast was at 7, not 12 ».

When the agent gets it wrong

The card is the moment to catch a bad edit. If the agent found the wrong entry (the rice instead of the chicken), say so: « no, the chicken — the meat row, not the carbs ». If the agent is about to change the wrong field (you said « 250 » meaning grams but the agent thinks you mean calories), call the field: « 250 grams, not 250 calories ».

If the agent matched multiple entries and asks which one (today’s meal has two chicken items — yesterday’s leftovers plus the fresh one), point with the most distinguishing piece: weight, position, or « the one I just logged ».

What makes the correction worth doing

Three things decide whether this correction lands cleanly: the pointer is unambiguous (so the agent edits exactly one entry, not all matching ones), the new value is the truth (a quantity you weighed, not a quantity you guessed-rounded-up), and the change applies only to the field you meant (quantity or food or meal type, not all three by accident). The system reads corrected meal logs the same way as originals — daily macros, weekly adherence, streak tracking — so a clean fix restores the signal, while a sloppy fix corrupts it twice over. Say what’s off, point at the one entry, and confirm the card.