Skip to content

Ask what to eat next

2 min read 2 tools Updated May 12, 2026

— Say it like this
What's my next meal?
2 more ways to say it
  • Next meal?
  • What am I supposed to eat next, and when?
— Here's how it goes

What you'd see in chat

  1. What's my next meal?
  2. Your next meal is the afternoon snack — whey shake with a banana, about 280 kcal and 30 g protein. Slot's flexible but most days you hit it around 4 pm. Want me to log it now, or remind you in 30 minutes?

  3. Next meal

    2/4 logged

    Afternoon snack

    snack

    280

    kcal

    30g

    Protein

    35g

    Carbs

    3g

    Fat

    • Whey protein isolate 30 g
    • Banana 1 medium

Three in the afternoon. You're between meetings, you ate breakfast and lunch already, and the next planned meal feels like it's getting close. You ask the agent — what is it, when, and what's on it.

What the agent needs to hear

Behind your sentence, the agent works backwards to three pieces: which day, which slot, and what’s currently logged. You don’t have to spell every one out. The default day is today, and the next slot is the first unlogged meal in the plan. If you ate breakfast and lunch but skipped the morning snack, the agent reads the morning slot as missed and points you to the afternoon snack instead.

Explicit overrides take precedence over inference. « What’s tomorrow’s first meal? » jumps to the next day. « What should I eat in an hour? » anchors to a target wall-clock and picks the slot closest to it.

Meal slot and timing — defaults and overrides

Most diet plans don’t have hard timestamps. They have an order — breakfast, snack, lunch, snack, dinner — and a flexible band where each typically lands. The agent uses your logged meals to anchor: if breakfast hit at 8 and lunch at 1, the afternoon snack lives somewhere in the 3-to-5 band by precedent.

A freshly activated plan reads less precise than one with two weeks of logs behind it — the agent has no pattern yet to anchor against. For days that veer off schedule (« starting work at 6 am tomorrow »), the agent rolls the band earlier in proportion. You’re not editing the plan; you’re nudging today’s read.

Targets are guidance, not a contract

The card shows targets for the next meal — calories, protein, carbs, fat — and the planned items the plan suggested. Both are guidance. The protein number is what the plan budgeted; the items are one valid combination that hits it. If you’d rather eat something different from the same total, log what you ate — adherence reads from the macros, not item-for-item match.

Portions follow the same logic. « 30 g whey » is the plan’s typical scoop; if yours is 28 g, log 28 and the math adjusts.

When the agent picks the wrong slot

If the agent surfaces the wrong meal — you wanted dinner but it showed the snack — name the one you wanted: « no, what’s planned for dinner? ». The slot name is enough. Same fix for the wrong day.

If the agent says all meals are logged and you know you skipped one, push back: « I didn’t actually have the morning snack ». The agent re-reads the day, marks the slot as missed, and either suggests catching up or notes the macros will land below target.

Why this is useful

Three things keep this question useful: the slot matches what you’re actually hungry for, the macros are the budget (not a recipe), and the portions are a starting point, not a requirement. The system reads meal-log adherence from macros, not from item-match; this question keeps the plan in your head without pulling out an app. Ask, eat, log, move on.

— Related