Smarter nutrition tracking with AI

AI food logging starts by solving one problem: knowing what you ate and being able to find it later. Cami lets you describe meals and other everyday details in natural conversation, and the matching miniapp holds the record. A single entry may need follow-up or confirmation; once the conversation is done, go back to where the record is actually saved and check it.

This guide is about how to log, check, and revisit. It does not offer personal nutrition prescriptions, and it never treats AI estimates as measurements. Keeping a clear line between the facts you state and what the system infers makes later reviews far more grounded.

One food record: state four things first

Give the date, the meal, the food, and rough portions whenever you can. If you forgot the portion, just say “not sure” rather than inventing a precise number to fill the gap. Foods with the same name can differ in preparation and amount, so a little context says more than a dish name alone.

To log something later, say plainly “log yesterday’s dinner”, then check which day was saved. For how chat and miniapps work together, see the Cami chat life-records guide.

Finish the required confirmations, then check the miniapp

Processing a record may require tool authorization or further confirmation from Cami. Complete the steps the interface actually shows you, then open the food-logging entry in miniapps and confirm the content was really saved. Do not assume every field landed correctly based on one chat reply.

• Date and meal: You logged yesterday’s dinner late. Was it understood as today’s lunch?
• Content and units: Are the food names complete, and are the portions still the rough values you gave?
• Duplicates: If you sent the same meal twice, are there two entries?
• Corrections: After adding or fixing something, go back to the entry and check again instead of trusting the chat alone.

Entries and fields change between versions. If something cannot be edited or failed to save, describe the specific problem first, then work with what the interface supports. Do not assume every operation completes silently.

Keep estimates, self-reports, and measurements apart

Text or photos of food do not directly provide exact portions, recipes, or nutritional composition. This guide makes no promises about the accuracy of photo recognition or calorie estimates. If the interface shows an estimate, keep it separate from sources like a food scale or package label; it is fine to leave unknowns uncertain.

Weight, exercise, and water intake are different kinds of information; when you log them, state the value, the unit, and the time for each. Food records also do not automatically tell you what you personally should eat or what is changing in your body. The value of logging is easy retrieval of what you told it; interpretation needs proper grounds.

Review a week by answering one question your records can support

Start with a question like “Which days this week have a breakfast record?”, then look at those dates. A missing record does not mean you skipped breakfast, and a system summary cannot fill in missing facts. If you want to keep logging, give yourself one short task rather than demanding a full report for every meal from day one.

For example, check after dinner whether anything from today was missed, and keep the scope of logging to what you choose to leave behind. For reminder settings, see the Cami reminder guide. To revisit moments from your day, the journal helps, but the actual food data is checked in its own tool.

FAQ: is more detail always better?

Do I need exact gram amounts every time?

Record what you actually know. If it was not weighed, say it is an estimate. Inventing numbers for completeness only makes later reviews harder to judge.

Will Cami automatically generate a diet plan for me?

This guide covers everyday logging, not diagnosis, treatment, or personal nutrition prescriptions. Do not treat record summaries or chat suggestions as conclusions of that kind.

Pick a simple logging habit from the life scenarios, verify one real record first, then decide whether to continue.