The recipe situation in most kitchens is a small disaster nobody talks about. There's the cookbook with the post-it on page 84. The screenshot of the magazine page from 2019. The bookmarked website that won't load anymore. The handwritten card from a parent that you photographed once and lost. The recipe you definitely made last winter that you can't find now.
The friction shows up at the worst time — Wednesday at 6 PM, you're trying to remember the chicken thing that worked, and instead you spend twenty minutes scrolling through your phone, give up, and order delivery. The good recipes you've already collected go unused because you can't find them, and the new recipes you save end up in the same graveyard.
A vault that holds all your recipes, with an agent that can find the right one fast and answer questions about what you've cooked, fixes the actual problem. The recipes themselves aren't the issue; the retrieval is. (For the looser, "remember what you've been cooking lately" angle, Documenting Recipes and Cooking Experiments Without Losing the Plot is the companion.)
One vault, one page per recipe
In Docapybara, each recipe gets its own page. Pages nest with no depth limit, OneNote-style, so you can group recipes into a Recipes parent page with whatever sub-structure makes sense — by meal type, by season, by who originally gave you the recipe, whatever fits how you actually think.
You don't have to commit to a structure up front. The agent searches across everything, so a flat pile of recipes is fine. Most people find a light grouping helps for browsing — Weeknight, Weekend, Baking, Holidays, From family — but the categories are for you, not for the agent.
A recipe page is just markdown. Ingredients at the top, method below, notes at the bottom. No template required. The page can hold a photo, the source URL if you clipped it from somewhere, and any tweaks you've made over time.
Clip from anywhere, paste it in
Recipes come from everywhere. Websites, magazines, cookbooks, friends, screenshots, the back of a package, a video where someone narrated the steps. The vault should be agnostic about where the recipe came from.
For websites, the simplest move is to copy the recipe text and paste it into a new page. Add the source URL at the top so you can find the original later if needed.
For PDFs — cookbook scans, downloaded recipe collections, restaurant takeaway menus you'd like to recreate — Docapybara converts uploaded PDFs to markdown automatically. Drop the file on a page and the agent can read what's inside it. From then on, you can ask things like "What recipes from the bread book use sourdough starter?" and the agent finds them.
For handwritten or photographed recipes, paste the photo on a page and add the text below it as you transcribe. Or use audio — read the recipe out loud, get a transcript, clean it up. Either way, the recipe ends up as searchable text.
For recipes from family — the kind your grandmother gave you on a card that you don't want to lose — paste the photo, transcribe the text, and add a note about who it came from and what's special about it. That metadata becomes important when you're trying to find "the apple cake my mother-in-law makes for Thanksgiving" two years from now. (Family stories living alongside the recipes is also part of A Notes Setup for Genealogy and Family History Research.)
The notes are the part that makes it yours
A recipe is a starting point. Your version of it — what you actually do, what worked, what you'd change — is the thing worth keeping. Most recipe apps lose this part. They store the original and treat your tweaks as an afterthought.
A Notes section at the bottom of every recipe page holds your version. "Doubled the garlic. Used yogurt instead of sour cream. Reduced the sauce too far the second time — pull it earlier next time." These are the notes that turn a recipe you cooked once into a dish you can reliably make again.
After you cook a recipe, take ten seconds to add a one-line note. "Made it for the dinner with the Bensons. They asked for the recipe." Or "Skipped the fennel; better without." Over time, the notes section is what makes the recipe yours.
The agent can pull these notes when you ask. "Which recipes have I noted as too spicy for the kids?" The agent reads across the vault and gives you the list.
A simple inline database for what you've cooked
For people who like a bit more structure, an inline database tracking the recipes works alongside the per-recipe pages. The :::database::: directive lets a small spreadsheet live inside a parent Recipes page. Columns might be: name, type (main/side/dessert/breakfast), source, last cooked, rating, notes.
The agent can update it. "Add tonight's dinner — that lemon chicken thing. Type main, last cooked tonight, rating great, kids ate it without complaint." The row appears.
This becomes useful when you're meal planning and trying to remember what you haven't made in a while, or what got the best reception, or what's quick on a weeknight. "Show me main dishes I've rated 'great' that I haven't made in the last two months." The agent reads the database and gives you the list.
You don't have to maintain the database perfectly. Even partial data is useful — the agent can work with what's there.
Searching by what you have, not by what you remember
The most magic moment with a recipe vault is when you can ask: "What can I make with the chicken thighs and the broccoli that's about to turn?" The agent reads across all your recipes and finds the ones that fit.
This is fundamentally different from the way most recipe apps work. They expect you to remember the recipe and search for it. The vault lets you start from what's in your fridge and work backward.
The same shape works for dietary needs. "What recipes do I have that work for the vegetarian guest coming Friday?" Or "What do I have that's gluten-free and takes under 30 minutes?" The agent searches across everything you've saved, including the notes you added about timing or substitutions.
Meal planning without it becoming a project
Meal planning is where most people give up on a recipe system. Building a week of meals from a database of recipes is a chore that nobody loves doing on a Sunday.
A small Weekly plan page handles it. The agent does most of the lifting. "Suggest five weeknight dinners for next week using recipes I've made before. Mix it up — not the same protein every night. Try to use the chicken in the freezer and the kale before it wilts." You get a draft week. You edit. You're done.
After the week, the agent can generate the shopping list from the planned recipes. "Make a shopping list from the meals planned this week, organized by section of the store." The list comes back. You leave with the right things and stop forgetting the one ingredient you needed for Thursday.
Most cooks also have a list of recipes they've bookmarked, screenshotted, or saved with the intention of trying. That list usually goes nowhere. A To try child page (or a section in your Recipes database with a status column) keeps these visible. The agent can rotate them up. "Suggest two new recipes from my To-try list for next week — one weeknight, one for Saturday." Forces some momentum on the queue without you having to think about it. The agent's web_search tool can pull current information when you're considering a new recipe. "Find a few highly-rated versions of [dish name] and tell me how they differ in technique." You get a summary with sources. You can take the bits you like and start a new recipe page from a synthesis instead of from one specific source.
Holiday and special-occasion recipes that don't get lost
Some recipes only come out once a year, which is exactly when they're hardest to find. The Thanksgiving stuffing. The Christmas cookies. The birthday cake variant your kid actually likes. The recipe a relative brings every Easter.
A Holidays parent page with one child page per holiday or occasion solves this. Each year you can add a note: "This year I doubled the sage and it was much better." Next year when you're prepping, you have last year's notes right there. The institutional memory of your kitchen — what worked, what didn't, what the family preferred — accumulates instead of being relearned each season. (For the same shape applied to home produce, Tracking Your Garden: Planting Schedules, Harvests, and Soil Notes covers it.)
The agent can pull a holiday plan together. "Show me everything I usually make for Thanksgiving, in roughly the order I cook it on the day." The vault becomes a kitchen game-plan.
A starter shape that works on day one
If you're moving from "recipes scattered across five places" to a vault, this is what we'd suggest:
- Recipes — parent page. One child per recipe. Add as you go.
- To try — list of recipes you want to try. The agent suggests rotations.
- Weekly plan — a working page for the current week's meals.
- Shopping list — generated by the agent from the weekly plan.
- Holidays — special-occasion recipes with year-by-year notes.
Five pages. No tag taxonomy, no required fields. The vault grows as you cook.
The point isn't to turn cooking into a database project. It's just that the recipes you've already loved should be findable when you want them, and the new ones you save should actually have a chance of getting cooked. A small amount of structure means weeknight dinner stops being a panic about what to make and starts being a question with an answer.
Try Docapybara free — start with the recipes you can already remember, and the next time you want one of them, the answer comes back in seconds.