Why this is hard to keep track of

  • Standing-up food doesn't register as eating, so it never gets recorded
  • By the evening the day's grazing is genuinely unrecoverable from memory
  • Opening an app for one biscuit is absurd, so it doesn't happen
  • The shared office tin is invisible to every tracker ever made

Worth recording

  • That something was eaten, and roughly where — the exact food matters less
  • What you were doing at the time, which is the actual pattern
  • Whether a meal preceded it, and how long before
  • The room, more than the food. Kitchens and desks dominate most logs

Cadence

Two seconds, at the time. Dictated is fine

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.

Mindless Snacking Chat

Handful of nuts, then two biscuits from the tin. Standing in the kitchen, about four.

Called 4 tools

  • log_snack(items: ["nuts", "biscuits"], at: "16:10", setting: "kitchen")
  • log_context(activity: "passing through", planned: false)
  • find_pattern(group_by: "hour")
  • compare_periods(metric: "snacks", group_by: "lunch_size")

Logged in two seconds. Four in the afternoon is comfortably your busiest snacking hour — 19 of 52 entries fall between three and five. The second cluster is around eleven, and both sit roughly three hours after a meal.

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.

Asking about the pattern Chat

Am I actually hungry at four, or is it just that I walk past the kitchen?

Called 3 tools

  • get_history(topic: "mindless-snacking", window: "6m")
  • find_pattern(group_by: "context")
  • compare_periods(metric: "entries")

Mostly the kitchen, on this data. You logged hunger below three on 14 of the 19 afternoon entries. Working-from-home days produce 15 of those 19, against four across the same number of office days — and the office has a snack tin too. That points at the route past the kitchen rather than at appetite.

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 mindless snacking

The same mechanics as everything else here, pointed at what actually matters for this one.

An entry is a sentence

Type it or say it. No item lookup, no portion field, nothing to complete before the entry counts — which is the whole reason this one survives past week three.

Or just a photo

A picture of the plate takes a second and records the thing descriptions are worst at. We store it against the entry; we don't estimate a calorie count from it and hand you the guess.

Context, not just food

Where you were, who with, what had just happened. In almost every log on this site the pattern turns out to live in the context rather than in what was eaten.

No streak to break

A gap in the record is a gap in the record. Nothing resets, nothing is lost, and nothing tells you that four missed days undid the month before them.

Readable across months

One rough fortnight reads as one rough fortnight when it sits on a six-month line — which is the view that changes what people believe about themselves, and the one a daily score can't draw.

Yours, and exportable

Everything you've written and every photo, out in one file whenever you want it — including the date range a dietitian or therapist asked you about.

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: The half of your intake that no recall-based food diary has ever captured, which is usually the half a dietitian is trying to ask about.

  • 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

No card required. Unsubscribe any time.

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.