See where today's macros stand right now

It's three in the afternoon. You've logged breakfast and lunch but you're not sure if there's room for the post-workout shake before dinner. You ask the agent for the day's standing — what you've eaten, what's left, whether you're on track.

What the agent needs to hear

Behind your sentence, the agent works backwards to two pieces: the date and which slice of the day you want back. Today is the default — « how am I tracking » with nothing else attached returns the full live snapshot for the current day. Yesterday or another date has to be named (« how did I close out yesterday? »).

The second piece is the slice. The default is the whole picture: consumed and remaining across calories and macros, every meal slot logged so far, what’s still queued if a plan is active. If you only care about one metric — « how’s my protein? », « what’s left on calories before dinner? » — the agent narrows to that read and skips the rest.

What you can ask for

The full live snapshot is the workhorse. It returns the day’s totals so far, the gap against your targets, a meal-by-meal breakdown of what was logged, and — when a plan is active — the slots still ahead. Most three-o’clock questions land here.

A single-metric read trims the surface: « how much protein left? » comes back as one number against one target. Useful when you already know you’re on track for everything else and just want to confirm one line. A next-meal suggestion goes a step further — « what should I have for dinner to hit my numbers? » asks the agent to use the remaining macros as a constraint and propose something that fits. And when an active plan exists, you can ask the comparison directly: « am I on plan for today? » reads consumed against the plan’s targets, not against generic macro goals.

How the read shapes the rest of the day

The point of this read is that it’s actionable. You check at three pm to decide whether the shake before dinner is on the table or off it. The number doesn’t just describe the day — it shapes the next meal.

If you’re on plan, the snapshot also tells you which slot is next and what’s queued for it. If you’re off plan, or no plan is active, the raw macro state is what you decide on. Either way, the system updates the moment you log — a re-read after the shake reflects the new total immediately, no refresh, no lag.

When the agent gets it wrong

If the numbers don’t match your gut, the read is the wrong one before the math is. The most common miss is the day: a late « how am I tracking » can pull yesterday if the request gets ambiguous timestamps. « Today, not yesterday » resets it.

The second miss is a logged meal that doesn’t appear in the breakdown — almost always because the log itself was incomplete or saved against the wrong slot. Fix the log first, then re-check; the snapshot only reflects what’s actually saved. The third miss is targets reading against the wrong plan. After a recent activation, the cache can serve the old plan’s totals for a few seconds — « refresh against the current plan » forces a clean read.

What makes the read worth trusting

Three things decide whether this snapshot is honest right now: all meals logged so far are actually logged (a missing meal log makes the « remaining » number look generous when it isn’t), the targets are from the active plan, not a stale one (mid-day activation can serve a stale cache for a few seconds), and partial-deviation logs are included (a half-logged meal still counts toward the day’s macros). The system uses this read as the live source of truth for what’s left in the day. A missing log here means a wrong number; a wrong number leads to a meal decision you wouldn’t otherwise make. Log first, check second.