Food tracking, reimagined for the AI age
The food journal you can talk to
Say what you ate, or photograph it. No database lookup, no barcode, no calorie box to fill in before the entry counts. Then ask what your own eating actually looks like — over months, with the numbers counted from what you wrote.
Works from the web app, or from Claude and anything else that speaks MCP. Founding accounts lock their price for life.
Called 4 tools
log_meal(items: ["sandwich", "crisps"], at: "13:30", setting: "desk")log_context(reason: "break", company: "alone")log_hunger(before: 3)find_pattern(group_by: "setting")
One sentence, four fields recorded. Nothing was looked up, estimated or scored — and the comparison at the end is a count of your own entries, not an opinion about them.
One system, two ways in
Not a chatbot bolted onto a calorie app
Plenty of apps have a chat window that can answer questions about your data. This one drives it. Both surfaces call the same registered tools, so anything you can do by tapping you can do by saying — and the reverse.
Tap it like any journal
A day, a photo, a note. Everything has a screen, because a single tap is genuinely the fastest way to log the breakfast you have four days a week.
Or just say what you ate
Useful for everything a form can't hold — the meal out, the evening that got away, the reason. And for asking the questions no food diary has ever been able to answer.
- "Leftover curry for lunch, ate it at my desk"
- "Dinner out with friends, sharing plates, a couple of glasses of wine"
- "Skipped lunch again — meetings"
- "Do the weekends actually undo the week, or does it just feel that way?"
- "Which of my usual dinners leaves me uncomfortable afterwards?"
Both surfaces call the same registered tools
One registry, one permission model, one log. A tool built for a screen is available to the chat the same day — and to any MCP client you point at your account.
The one-second entry
Photograph the plate and get on with your dinner
Portions are the one thing a description is genuinely bad at and a photograph is genuinely good at. A plate looks like a plate; two plates side by side three weeks apart are unmistakable.
So a photo is a complete entry here. Add a word if you want to, or don't — the picture, the time and the day are already more than most food diaries retain by the end of the second week.
- A photo is a whole entry. Nothing else is required
- Stored against the day, searchable months later
- Exportable with everything else, which is what makes it worth showing a dietitian
- Never analysed for anything except being a record of a meal
What we don't do with a photo
Every app in this category is racing to tell you a photo of your lunch was 640 calories. That number is a guess with a decimal point on it — it cannot see the oil in the pan, the size of the plate or what's underneath — and the harm isn't the guess, it's that you'd make decisions with it for a year.
- No calorie estimate presented as a measurement
- No macro breakdown invented from pixels
- No score, no grade, no red or green
- No comment on your body. The photos here are of food
What a photo is excellent at is being a truthful record of the meal. We keep it as exactly that.
Where the numbers come from
The model never invents your patterns
This matters more here than it looks. A food log that flatters you is worse than no log at all, so the language model reads what you said and picks which operations to run. Your record does the counting.
It chooses the query, not the answer
"Do the weekends undo the week?" becomes a comparison across your own entries. The model decides what to compare; the arithmetic happens against the log.
Counts, with the counts shown
Answers come back with the numbers behind them — 13 of 18, not "you tend to". If you want to see which entries produced a figure, you can.
It says when the data is thin
Eleven entries is eleven entries. Where a pattern isn't there yet, the answer says so rather than rounding a coincidence up into a finding.
What people track here
Four kinds of page, because they're four different things
A pattern you want to understand, a direction you've chosen, a protocol you're following, and eating alongside a medication somebody else is managing are not the same kind of thing. Filing them under one heading would be making a claim about all four.
Eating patterns
How you eat rather than what. Emotional eating, late nights, snacking, portions, hunger. No targets and nothing to comply with — these pages describe eating, they don't correct it.
Goals
Something you're working toward, with your own definition of it. Nothing here calculates a target for you — including the two pages that aren't about weight and the one about gaining it.
Diets
Protocols people follow, described rather than sold — what each one actually involves, where the evidence is thin, and who should talk to a clinician before starting.
Eating on a GLP-1
Its own section rather than a diet, because it isn't one. Your prescriber runs the medication; this runs the notebook — an informal record of what you ate, what stayed down, and what changed.
Three months in
The part every food diary was missing
Food diaries have always been write-only. You keep one for six weeks, take it to an appointment, and the reading is done by eye in four minutes — which is why almost nobody keeps one for six months.
A log that can be queried is a different object. The questions people actually have are comparative and awkward — is it the sleep or the skipped lunch, do the weekends really matter, which dinners leave me uncomfortable — and every one of them is answerable from entries you already made, in the time it takes to type it.
Called 4 tools
get_history(window: "3m")find_pattern(group_by: "evening_eating")compare_periods(metric: "evening_eating", group_by: "lunch")compare_periods(metric: "evening_eating", group_by: "sleep")
Four tool calls against your own entries. The model picked the comparisons; it produced none of the numbers.
Bring your own assistant
It works from Claude too
The same tools are exposed over MCP, so you can log a meal and ask about your own patterns from the assistant you already have open — under scoped, revocable access you grant per client.
If you're already talking to something all day, the lowest-friction food log in the world is the one that lives where you already are.
What that gets you
- Log a meal without opening another app
- Ask about your own history from the client you already use
- Scoped access per client, revocable in one click
- The same tool registry the web app uses, with the same permissions
Questions
The things people ask first
Does it count calories?
No — and not with the numbers hidden, either. There's no calorie field, no food database and no daily total. What you get instead are counts of your own entries: how often something happened, when, and what was going on around it. If you specifically want gram-level precision, weigh your food and use a macro app; that's the honest answer.
Can I just take photos?
Yes. A photo is a complete entry — the picture, the time and the day are already more than most food diaries retain past week two. Add a sentence when it's worth it. We store the photo as a record of the meal and don't estimate a calorie count from it.
Will it tell me what to eat?
No. It doesn't design a diet, score a meal or sort food into good and bad, because it has no basis for any of that — it has seen your entries and nothing else. It's a notebook that can do arithmetic and answer questions about itself.
What if I miss a few days?
Then those days are empty. Nothing resets, no streak breaks and nothing will tell you you've fallen behind, because a streak is exactly the mechanic that makes people quietly stop logging the days that would have been most informative.
I've had an eating disorder. Should I be using this?
That's a real question rather than a disclaimer, and for some people the answer is no — any form of food tracking can make things worse, and it's worth deciding with a clinician rather than an app. If you're in treatment and have been asked to keep a record, this is built to be that record: no targets, no scores, nothing counting anything down.
Where does my data go?
Into your account, exportable in full — photos included — whenever you want. What you send to the chat is processed by a model provider to produce a reply; your log isn't training data and isn't sold. The privacy page sets out exactly what's sent and when.
When can I use it?
The waitlist is open now and we're building with the people on it. Founding accounts lock their price for life, and the fastest way to shape what gets built first is to tell us what you've been trying to keep track of when you sign up.
Early access
Start with whatever you've been trying to keep track of
Tell us what it is 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 target calculated on your behalf
- Export everything you've logged, photos included, whenever you want
- We read every answer to the last question. It's the reason it's there
A food journal you'll still be keeping in month six
Founding pricing is locked for accounts opened during early access.
Founding accounts lock their price for life. No card required.