The braise you made in February — the one your partner asked about three months later — is gone. Not gone-gone, but functionally gone. It's in a screenshot on your phone, or a half-typed note that just says "more salt next time, less wine," or maybe a printed page somewhere with a coffee ring on the corner. By the time you want to repeat it, you're starting from scratch.
Most home cooks live with this. Recipes accumulate across screenshots, bookmarks, cookbook margins, and memory. Tweaks are remembered for a week and then quietly lost. The good versions of a dish never quite become the version you make every time, because there's no place where the "best so far" lives.
A vault that holds recipes, your edits, and the small notes you make while cooking fixes most of it. The agent does the searching when you want to cook again. (For the more retrieval-focused take, Your Recipe Box: Stop Losing the Good Ones is the companion guide.)
One page per recipe, with the version history right there
In Docapybara, every recipe gets its own page. The page can hold the original source (a paste from a website, a photo of a cookbook page, a transcript of a phone call with your aunt), the version you actually cook, and a running log of tweaks underneath.
Pages nest with no depth limit, OneNote-style. So a parent page called Recipes can have child pages organized however you actually think — by cuisine, by protein, by season, by who taught you. Whatever shape your kitchen brain already uses, the vault matches.
The agent treats this whole nested structure as one searchable pile. "Find me the chicken recipe with the lemon and capers, the one I made twice last fall." The answer comes back with a link to the page.
Capture the source without retyping it
Every recipe has a source — a website, a cookbook, a friend, a half-remembered restaurant. The friction of retyping is what kills most recipe collections before they start.
For web recipes, paste the URL on the page and let the agent pull the relevant content into clean markdown underneath. For cookbook pages, photograph them and drop the image on a page; an upload of the page as a PDF works the same way. PDFs upload and convert to markdown automatically via the agent's PDF pipeline, so the recipe's actual ingredients and steps become searchable text rather than a flat image you can never grep.
For verbal recipes — the phone call where your grandmother explained a sauce — record the conversation (with permission) and drop the audio on the page. You get a transcript with speaker labels, so you can see exactly which step she said to do first, and exactly the phrase she used about the texture. "Cook it until it looks like wet sand" is the kind of detail that gets lost otherwise.
The tweaks belong on the same page as the recipe
The most common reason recipes drift over time is that the tweaks live somewhere else. You scribble "reduce by half" on a printout, but next time you cook from the original. The third time you just guess.
A Notes section underneath each recipe — or a small inline database of attempts — keeps the iteration honest. The :::database::: directive lets a small spreadsheet live alongside the prose, in the same page. Columns for date cooked, what you changed, who ate it, what you'd do differently next time.
The agent can update it. "Add a note to the braised short ribs page — cooked tonight, used red wine instead of port, simmered an extra forty minutes, came out better than last time." Row appears with the date filled in. Three months from now, the version that actually works is the one with the most rows.
For dishes you've made many times, ask the agent to summarize the trajectory. "Look at every time I've cooked the focaccia and tell me what the latest stable version looks like." You get a summary grounded in your actual notes, not your impression of how it's evolved.
A daily kitchen log for the experiments that aren't recipes yet
Some things you cook aren't recipes. They're experiments — a sauce you made up, a way of treating a vegetable that worked, a leftover transformation that turned into the best lunch of the week.
A Kitchen log page (or one entry per notable thing) catches these before they evaporate. Voice is the right tool here, because your hands are usually full of olive oil. Tap record, talk for thirty seconds. "Roasted the cauliflower at 450 instead of 400, added the tahini sauce while still warm, the warmth made the sauce loosen and coat better. Try this with broccoli too." The transcript lands on the log with a timestamp.
A few weeks later, when one of those experiments turns into something worth repeating, the agent can promote it. "That cauliflower thing I wrote up a month ago — turn it into a clean recipe page with ingredients listed and steps in order." You get a draft recipe page; you adjust the parts the agent guessed wrong; the experiment becomes a recipe.
A pantry and equipment context the agent can use
The cooking advice that's useful to you depends on what's actually in your kitchen. The cookbook recipe assumes a Dutch oven you don't have, a fish you can't get, a fermented thing you've never bought.
A Pantry & equipment page — what you actually keep stocked, what tools you have, dietary constraints in your household — gives the agent a real context to reason in. "Suggest a weeknight dinner I can make from what I have, that takes under forty minutes, and avoids the dairy thing." The answer is grounded in your real pantry, not a generic LLM guess.
For meal planning across a week, this becomes useful. "Plan three dinners for Tuesday through Thursday, using the chicken thighs in the freezer and the kale that needs eating, and make at least one a leftover-friendly one." The agent can pull from your existing recipes, propose new ones, and write a small grocery list for the gaps. (Gardeners using their own harvest as inputs may also want Tracking Your Garden: Planting Schedules, Harvests, and Soil Notes.)
Inline databases for ingredient swaps and seasonal rotations
For cooks who care about substitutions — gluten-free baking, dairy-free desserts, low-sodium adaptations — an inline swap database is genuinely useful. Columns for ingredient, substitute, ratio, and notes about which kinds of recipes the swap holds up in.
The agent reads it when adapting a recipe. "Take this brownie recipe and swap the dairy out using my swap database — give me the adjusted ingredient list and tell me which step changes." Comes back with the swapped recipe and a flag on any step where the substitution behaves differently from the original.
For seasonal cooking, a What's in season page with rough month-by-month lists for your region — built up over a year or two — gives the agent something to anchor on. "Suggest a salad I haven't made recently, using April things from my seasonal page." The recommendations stop being generic.
A related habit some cooks find helpful: a Restaurant dishes worth recreating page. The dish, the place, what made it good, your best guess at the technique, any attempts you've made at home. Some entries stay aspirational forever; some turn into your best home recipes after a year of guessing. (For the broader habit of catching the moment something clicks, see The Capture Habit: Remembering the Things That Actually Matter.)
A shape that works on day one
If you're moving from "recipes scattered across a phone, a laptop, and a shelf" to a vault, this is what we'd suggest starting with:
- A Recipes parent page — child pages by whatever organizing principle your kitchen brain uses. No need to be consistent.
- One page per recipe — source on top, your version underneath, a notes log at the bottom.
- A Kitchen log page — voice notes for experiments, things to try, leftover ideas.
- A Pantry & equipment page — what you actually own, dietary constraints, what's reliably in stock.
- An inline database for tweaks if you cook the same things often, or for swaps if you adapt recipes a lot.
That's it. Nothing colour-coded, no template required. The vault grows the way your cooking does, because the things you actually make will accumulate notes and the things you tried once won't.
The point isn't to turn cooking into a database project. It's that the small amount of structure means the dish you loved in February is findable in May, the tweak you discovered in October survives until next October, and the agent has enough material to actually help when you ask "what should I cook tonight?"
Try Docapybara free — start with three recipes you actually cook and a kitchen log, and see what your cooking looks like with the version history right next to the recipe.