GLP-1 · Food Diary
A food diary for the months when hunger stops making the decisions
Almost everyone describes the same strange adjustment. The thing that used to organise the day — being hungry — simply stops turning up, and with it goes the mechanism you were relying on to know whether you'd eaten. Meals become small, irregular and genuinely hard to recall by evening, because nothing about them registered as an event. Then the clinic asks what a typical day looks like now, and the honest answer is that you have no idea. That's the gap a one-line record closes, and it closes it in about four seconds a meal.
For anyone on a glp-1 who wants an honest record of what they're actually eating now.
Where this fits
What this sits alongside
Your prescriber runs the medication — the dose, the schedule, the reviews, the bloods. This runs the notebook: what you ate, what stayed down, and what changed. Those are two different jobs, and only one of them belongs in an app.
Why this is hard to keep track of
- Meals are small and irregular, so nothing about them encodes as an event
- The question flipped from "did I eat too much" to "did I eat at all", and no app asks that
- Calorie apps are built for restraint, which is the opposite of the problem now
- "What does a typical day look like?" is unanswerable after three months of this
Worth recording
- What you ate and roughly when — a sentence is plenty
- Whether a meal happened at all, which is the more useful field here
- What stayed down and what didn't
- How much appetite there was, since it moves week to week
Cadence
A line per meal when you can. A tick when you can't
In practice
Say it once, or photograph it
The entries most worth having are the ones made at the exact moment nobody wants to fill in a form. A sentence — typed, dictated, or replaced entirely by a photo of the plate — is a much lower bar, and it carries the context a calorie field would have thrown away.
Called 4 tools
log_meal(items: ["soup, half a bowl"], at: "13:00", appetite: 1)log_meal(items: ["chicken, a few bites"], at: "19:30", appetite: 1)log_note(text: "ate because I should, not because I wanted to")get_history(metric: "meals_per_day", window: "30d")
Every figure here was counted from entries you made. The model chose which tools to call — it doesn't score the meal, estimate calories from a photo, or decide what any of it says about you.
And then ask
The question the log can answer
Months of entries hold real answers to the things you've been guessing at, and reading them properly has always meant a spreadsheet and a free evening — which is exactly what nobody has.
Ask in plain language. The answers come back with the counts behind them, including when those counts are too thin to mean anything yet — which is the more useful answer far more often than people expect.
Called 3 tools
get_history(topic: "food-diary", window: "6m")find_pattern(group_by: "context")compare_periods(metric: "entries")
Counts and averages over your own entries, nothing more. Where the data is confounded or too thin, the answer says so instead of rounding it into a conclusion.
What it does
Set up around food diary
The same mechanics as everything else here, pointed at what actually matters for this one.
An entry survives a bad week
A sentence, or a tick that a meal happened at all. On the weeks when eating is genuinely hard, the log has to cost less than the meal did — otherwise the record stops exactly when it gets interesting.
Photos, for the thing descriptions miss
Portion sense recalibrates within weeks and nobody can see it happening. Two photographs eight weeks apart settle it instantly.
Mark the date something changed
Your prescriber decides what changes; the log just notes when, so the fortnight either side can be counted against each other instead of recalled.
Side effects with the meal before them
Nausea on its own is a complaint. Nausea with what you'd eaten, how long it lasted and where it fell in the week is something a clinician can work with.
Watching for eating too little
The risk here is rarely eating too much. Missed meals and meals without a protein source are counted and shown to you, because appetite has stopped being the thing that would have told you.
Formatted for the review
Export the window you were asked about, photos included, and take it in. It's the answer to the first question at every appointment.
The reason a lot of people start
Something to actually bring to the appointment
You get fifteen minutes, and the first question is always some version of "so what does a normal week look like?" — which nobody on earth can answer accurately from memory.
What this gives you: An actual record of what you've been eating, which is the first question at every review and the one nobody can answer accurately once meals stopped being memorable.
- Export the date range you were asked about, as a file you can print
- Photos alongside the entries, which say more than any description
- Counts and timings rather than an impression of the worst week
- Nothing shared anywhere unless you choose to share it
What it won't do
- Score a meal, or sort food into good and bad
- Estimate calories from a photo and present the guess as a number
- Set you a calorie target, a macro target, or a weight
- Run a streak you can break, or tell you that you've fallen behind
- Comment on your body. The photos here are of food
- Diagnose anything, or suggest that a pattern is a diagnosis
It's a notebook that can do arithmetic and answer questions about itself. Deciding what any of it means is a job for you and the people advising you.
Early access
Start with what you're already trying to hold in your head
Tell us what you've been trying to keep track of and we'll set it up with you — recording the thing that's actually useful, at a cadence that survives a bad week.
- Founding accounts lock their price for life
- No card, no trial clock, no notification designed to make you feel behind
- Export everything you've logged, photos included, whenever you want
Also here
The rest of the picture
These overlap constantly, which is the point — the answer to a question about one of them is very often sitting in another one's data.
Protein
A sentence a meal. No weighing, no packets
Side Effects
When something happens. Ten seconds, at the time
Portion Changes
A photo when it's a proper plate of food. Not every sip of soup
Titration Weeks
Mark the date, then carry on logging as normal
Coming Off
Much lighter than while you were on it. A few entries a week is plenty
Keep the record without it becoming another job
Founding pricing is locked for accounts opened during early access.
Founding accounts lock their price for life. No card required.