There's no "add meal" button in metrIQ. You tell Sophia what you ate, in your own words, and she logs it. That's the whole interface — the composer even prompts you with "Tell Sophia what you ate…" rather than a form to fill in.
What to type
Sophia is built to take ordinary descriptions, not a structured format. A few real examples of what works:
- "had a chicken salad, about 500 cals and 40g protein for lunch"
- "two eggs and toast for breakfast"
- "just had a coffee with oat milk, and a banana, and some almonds"
That last one logs three items from a single message — you don't need to send them one at a time. Say what you ate and when (if it wasn't right now), and she'll sort out the rest.
Time, and logging for an earlier day
Every entry is stored with the exact moment it happened, and that's what orders your diary and decides how meals are grouped — two items logged at the same time show up together as one meal card, a different time splits them into two. If you don't mention a time, Sophia infers one from the meal slot — breakfast lands around 8am, lunch around 1pm, dinner around half seven — so stating the real time, even roughly ("about 7", "just before nine"), replaces her guess with what actually happened.
You don't have to log the moment you eat. Catching up later works equally well: "yesterday I had a big cooked breakfast, eggs and bacon" or "forgot to log lunch on Tuesday, a chicken wrap" both log correctly against that day. You can go back as far as the day you joined metrIQ; you can't log the future — tell her about a meal you haven't had yet and she'll log it as happening now instead.
How she works out portions
If you name a food you've saved to your pantry, Sophia matches it and logs the macros from that saved food exactly — not a guess, the real numbers you entered. If it's something new, she estimates the calories and macros herself from what you've described, filling in anything you didn't mention. Give her a quantity when you have one — "150g of rice" logs more precisely than "some rice" — but if you don't, she'll log a sensible estimate rather than stall the conversation asking for one. Vague is fine; wrong is fixable.
Correcting her
If she guesses wrong, say so in your next message: "actually that was closer to 700 calories" or "that wasn't a burger, it was a pizza." She'll log the corrected version and quietly remove the one it replaces, so the total stays right and nothing gets double-counted. This is different from adding to a meal — if you forgot to mention something and want it added rather than swapped in, say that instead ("also had a coke with lunch") and it joins the meal without touching what's already there.
You can also correct or remove something logged a while ago, not only the last message — "delete my last weigh-in" and "scratch that lunch, I didn't actually eat it" both work, and Sophia will ask if she isn't sure which entry you mean.
Why this instead of a form
A form makes you translate what you ate into fields before you can log it. Chat skips that step — you say the thing, the way you'd tell a friend, and Sophia does the translating. It's slower to get exactly precise this way than typing numbers into boxes, but it's much faster to actually do, which is the part that matters for logging every day.
If something isn't logging the way you expect, ask us.