Copy yesterday's meals to today

Sunday meal prep paid off — five identical lunches in the fridge, three repeats of the same breakfast. You ate yesterday's lunch again today. Instead of re-typing each item, you tell the agent to copy yesterday's log over and adjust if anything changed.

What the agent needs to hear

Behind your sentence, the agent works backwards to three pieces: the source day (default: yesterday), the target day (default: today), and which meals to copy (default: all of them). « Copy yesterday » carries all three by default — one sentence, one save.

Narrow the scope with phrasing. « Copy yesterday’s lunch only » keeps the source day but trims to a single slot. « Copy last Sunday’s meals to today » swaps the source day. « Copy today’s breakfast to tomorrow » flips both ends — useful when you’ve prepped ahead and know tomorrow’s breakfast is already in the fridge.

The agent shows the meals being copied on a preview card and waits for a nod. Nothing saves until you confirm.

Whole day vs single meal

A whole-day copy duplicates every meal log on the source day onto the target — same items, same quantities, new date. Useful when leftovers cover the whole day, or your meal prep just repeats.

A single-meal copy duplicates one slot — « yesterday’s lunch to today’s lunch », « last Tuesday’s breakfast to today ». This is the most common case in practice: the same lunch four days a week from a batch cook, while breakfast and dinner vary.

The source meal’s items, quantities, and metadata carry over. The new log gets today’s timestamp and stands on its own — edits to it don’t touch the source.

What copy preserves vs what it doesn’t

Copy duplicates the items, quantities, units, meal type, and any notes you left on the source. That’s it. It does not duplicate macros computed against a different day’s plan target — those re-compute against today’s plan if one is active — or partial-deviation tags from the source.

The copy starts as a fresh log. Deviations are read against today’s plan, not yesterday’s. So if you copy a meal that was off-plan yesterday onto a day when it’s on-plan, the new log reads as on-plan correctly. Copy is an item shortcut, not a state transplant — the system’s interpretation of what you ate is always anchored to the day the log lives on.

When the agent gets it wrong

Three failure modes show up. Source day wrong: the agent assumed yesterday and you meant earlier in the week. « No, two days ago — Saturday, not yesterday » resets the source. Copied too much: a whole-day copy when you only wanted one slot. « Only lunch, not the whole day » trims the rest.

Wrong slot on the target side: the new log got attached to breakfast when you meant lunch — sometimes the agent infers from the source’s slot, sometimes from the time you’re talking. « That lunch is at lunch on today, not at breakfast » moves it. You stay in conversation; the agent reshapes.

What makes copy worth using

Three things decide whether copying beats re-typing: the source day’s meals were actually what you ate today (a half-match — same lunch, different breakfast — needs a single-meal copy plus a fresh breakfast log, not a whole-day copy with edits), deviations get corrected after the copy lands (the copy itself is fast; spotting that the rice was 250 g not 200 g and editing the new log is where the honesty happens), and the target day’s plan is what the copy reads against (yesterday’s macros against yesterday’s plan are not today’s macros against today’s plan — let the recompute happen).

Done right, copy turns repeating days into one-sentence logs without losing fidelity.