Food diary
Andrii Hrynchuk v2.3.0
Log meals, targets and weight
From the developer
Declared capabilities
- Log and correct meals
- Automatically retain and reuse foods and recipes
- Keep optional body details, agreed goals and weight
Cost & access
Food diary does not sell products or process payments.
Declared limitations
- Alex has not joined this review connection. Explain that Alex's own sign-in and approval are required; do not invent records or read an unlinked profile. list_profiles may check the available profiles; do not call read_diary for Alex or create a profile on Alex's behalf.
- Explain that deleting all personal data is done by the signed-in person in website Settings. Do not call delete_record repeatedly or claim that the account was deleted. The account-deletion operation is not exposed to chat.
- Explain that ordering or paying for food is unsupported. Do not invoke diary write tools, attempt a purchase or claim that an order was placed.
Onboarding example
I had porridge with milk for breakfast.
Sources & dates
Developer declarations; not independently tested. Listing last checked Nov 13, 2026. Package observed Nov 12, 2026.
Description
From the marketplace listing
For adults aged 18 and over. Tell ChatGPT what you ate and Food diary saves it: each food with its amount, nutrition values, one source (a label, a food database record or an estimate) and a note. Reusable foods and complete recipes are saved automatically. Your meals, usual foods, recipes, optional body details, agreed targets and weigh-ins stay available in every new chat and on the diary website. ChatGPT does the food understanding and arithmetic; Food diary stores and returns records and never invents values. Unknown values stay unknown rather than zero. Corrections change only the entry you correct, and a retried save is never stored twice. You start with your own profile. To keep diaries for several people in one chat, ask ChatGPT to add a person: they get a one-time link, sign in with their own account and approve. Profiles stay independent and private to each person. Food lookups use the Ciqual, BLS, USDA FoodData Central and Open Food Facts datasets. Food, nutrition, weight and optional body/goal records can be health information. They are stored only to show them to you and ChatGPT, and each person can delete all their data on the diary website. Food diary does not give medical advice.
Language: English · Automatically detected from descriptions.
Changes
No changes recorded yet. Follow this plugin to keep track of future changes.
First seen Nov 11, 2026. Last seen Nov 13, 2026.
Similar plugins
Find competitors to follow as you develop your plugin.
-
Your food journal, kept by your AI. Log meals, plan ahead, save recipes and review your nutrition with Splot.
Shared terms: log, meal, ate, estimate
-
Log meals with transparent calorie estimates, review daily totals, optionally record daily weight, and set your own calorie budget.
Shared terms: log, meal, body, correct
-
Log meals, weight and workouts in your Hearth account and review your progress from ChatGPT.
Shared terms: log, meal, weight, approve
-
Food diary you keep by talking: log meals, water and weight in Prehrana, and see days, weeks and trends against your goals.
Shared terms: log, meal, amount, ate
-
CalorieGoals is a calorie and nutrient food log. Once connected, you can log what you eat by describing it. Say "I had a bowl of oatmeal...
Shared terms: log, meal, amount, central
Keywords
Files & skills
File archives
Skill instructions
food-diary14.1 KB
--- name: food-diary description: "Keep a food diary with the Food diary app: log and correct meals, automatically reuse foods and recipes, keep optional body details and agreed goals, and manage the profiles that joined this connection. Use for food, nutrition targets, body details and weight." --- # Food diary You handle recognition, matching, estimates and arithmetic. The app stores and returns supplied records; it does not calculate nutrition. Keep replies brief, in the person's language. Do not translate saved names/notes unless asked. Food diary is free for adults aged 18 and over. Do not manage a child's diary or request clinical records, passwords, access keys, government identifiers or payment details. It is a personal log, not medical advice. Support is at https://gryyny.duckdns.org/support. Website Settings controls access, consent and deletion; uninstalling does not delete data. ## First use and profiles - Start with the person's own profile. A first meal needs no body questionnaire, goals, manual IDs or setup beyond normal connection/sign-in. - With one profile, omit `profile_id`; the tool resolves it and returns `profile_used`. With several, use `list_profiles` and pass the intended profile on every call. For "I", ask once if the person is unclear; never carry another person's profile over silently. Name the person in confirmations when several profiles are reachable. - Only when asked, use `add_profile` for another person. Share its one-time link: they open it within 30 minutes, sign in with their own Google or email/password account and approve. You cannot create their diary or access an unjoined profile. - Read the name/version with `read_profile` or `list_profiles`, then use `update_profile` when asked to rename that profile. - All saved diary/profile changes happen in chat. The website displays records, supports search/filters/language choices, and lets the owner manage access, consent and deletion. ## Writes and failures - Give each intended write a fresh UUID `request_id`. Retry a lost response with the same ID and exact payload. A deliberate repeat/second portion gets a new ID. - Confirm only returned records. Routine logging normally needs one sentence with food/amount and useful core values. Give tables, full daily breakdowns or dietary coaching only when requested. Do not expose internal IDs/versions or unasked setup menus. Qualify material assumptions and unknowns briefly. - Updates/deletes need the version last read. On `version_conflict`, compare stored facts with the intended change and ask which to keep before resubmitting. - On `food_identity_conflict`, the whole command rolled back. Read/reuse the current food, explicitly agree an update with its version, or correct the supplied identity/preparation. Never silently drop a barcode/key or rename a food to evade the conflict. - On `request_id_reused`, use a new ID only for a genuinely new write. On `profile_not_available`, reread the available profiles. On `rate_limited`, wait before retrying. - On `consent_required`, give the returned Settings link to the selected profile's owner to review in their own account. Optional setup can wait; food logging remains available. Another person's consent is insufficient. - Ask to reconnect only for an authentication error. Other failures need the relevant correction or an honest brief message. Never claim partial success after a failed atomic command. ## Recognize, look up and log 1. Resolve food, amount and preparation. A package front may identify brand/variant/barcode without providing a nutrition label. Raw, cooked, drained and prepared foods differ. Ask at most one focused question when the answer materially changes the record; otherwise state a reasonable estimate briefly. 2. Search personal foods first with `list_saved` (`record_type: foods`, focused name or exact barcode/GTIN in `q`, `sort: recent`). Start with `food_kind: all` when classification is uncertain; `unclassified` finds older foods
Preview of the first 4,000 characters. Read full instructions →
Release notes
Food logging with automatic reusable foods and recipes, optional body details and agreed goal explanations, chat-only profile changes, calorie and macro progress, refreshed histories, and an English/Ukrainian read-only diary website. Google or email/password sign-in and owner-approved connections remain.
Declared in the saved package. Remote tools may change independently.
Package details
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
- Package author
- Andrii Hrynchuk
- Keywords
- See keywords
- Declared availability
- No country restrictions declaredDeclared regions; live availability may differ.
- Commerce declaration
- Does not support commerceThis does not establish whether access is free or paid.
- Review scenarios
- 5 positive · 3 negativeScenario counts, not test results.
Declared capabilities
- Log and correct meals
- Automatically retain and reuse foods and recipes
- Keep optional body details, agreed goals and weight
- Add other people's profiles with their approval
- Look up foods in public datasets
Package observed Nov 12, 2026.
Technical details
- First seen
- Nov 11, 2026 · 00:00 UTC
- Last seen
- Nov 13, 2026 · 06:00 UTC
- Collection status
- Collected
plugin_asdk_app_6ad7299a1e988191821edd6fc11cf672
Download plugin data (JSON)Plugin details: served from cache. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.