Why Sage Remembers Your Family's Allergies and Dietary Needs

Mention a nut allergy to Sage once. Six weeks later, she still won't suggest peanut sauce. That's the difference.

Most AI assistants forget you between sessions. You tell ChatGPT on Monday that your nephew has a peanut allergy and on Wednesday it cheerfully suggests pad thai with peanut sauce, because Wednesday is a fresh conversation and Monday is gone. The session ended. The memory ended with it.

That's fine for one-off questions. It is not fine for cooking for a family. Cooking for a family is the same conversation, every week, for years — and the conversation has stakes. The wrong ingredient is not a typo. The wrong ingredient is an EpiPen at the kitchen table.

This is the post about why Sage is built differently, what she remembers, what she does not, and why families with real dietary complexity end up using her on every meal plan.

The forgotten-allergy problem

Here is what it feels like the third time an AI forgets your nut allergy.

The first time, it is fine. You explain the situation. The AI generates a peanut-free dinner. You feel a little hopeful — finally, something faster than reading every label.

The second time, you have to explain again. The conversation is fresh. The AI has no idea who you are. You patiently retype: my nephew has a peanut allergy, please plan around it. It does. You sigh.

The third time, you stop. Because the third time you realize you are doing the cognitive work AND the AI is doing the cognitive work, and yours is the only one that compounds. The AI starts at zero every time. You don't.

The thing about cooking for a family with real dietary needs is that it is not a one-time problem. It is a forever problem. Mom is lactose intolerant for the rest of her life. Your nephew's peanut allergy doesn't expire. Dad has been on warfarin for eight years and will be for eight more. The kid going through a "nothing green" phase will eventually grow out of it, but probably after dinner stops being a battlefield.

Tools that forget make you do all the carrying. They are not assistants. They are a slightly faster way of typing the same constraints into a search bar over and over.

Why most AI tools forget

This isn't a flaw. It's how they're built.

Most AI chat tools — including the big general-purpose ones — operate on something called a context window. The context window is everything the AI can "see" at once: your messages, its replies, any documents you've pasted in. It's huge by historical standards. It is still finite, and it is still tied to the session.

When the session ends, the window resets. The next conversation starts fresh. Anything you taught the AI about your family in last Tuesday's chat is gone unless you copy-paste it back in. Some tools have started layering "memory" features on top, but most are shallow — they remember a few facts you've explicitly tagged, not the running portrait of your family that real meal planning requires.

The result: you, the cook, become the persistent memory layer. You carry the running list of who can eat what. The AI is just a faster typist, not a partner.

That is not the kind of help you need at 5:30 PM on a Tuesday when you are looking at the open fridge and wondering what to make for a family of five with three constraints.

Sage is different (and how)

Sage is built on top of a persistent memory layer called Wirable. Wirable's job is to carry forward, across every session, every conversation, every meal plan, the things about your family that don't change between Tuesdays.

Concretely: when you tell Sage your nephew has a peanut allergy, that fact does not live in the conversation. It lives in your family's profile. The next conversation, the next meal plan, the next recipe suggestion — all of them filter against it automatically. You don't re-explain. You don't re-tag. You don't re-paste. You just get back the meal plans that are correct for your family.

This is the part competitors can't easily copy. Building a real persistent memory layer for cooking is harder than it looks. It is not just storing the words "peanut allergy" in a database. It is knowing that "peanut allergy" rules out peanut sauce, peanut oil, satay, pad thai (typically), some processed crackers (cross-contamination risk), and that sunbutter and tahini are reasonable substitutes. It is knowing that lactose intolerance is different from a milk allergy is different from veganism — three constraints that look similar and produce three different recipe suggestions. It is knowing that "kosher" is not a single rule but a family of rules that depend on the family's level of observance.

Sage's job is to be the part of your kitchen that remembers all of this so you don't have to. That is the entire pitch.

What Sage remembers

The memory layer is wide on purpose. The same family member might have all of these layered on at once: a religious dietary law, a medical restriction from their cardiologist, a kitchen-equipment limitation, and a kid-being-a-kid food preference that's been going for five months. A tool that remembers any one of those but not the others is still making you do most of the work.

Here is what Sage will carry forward across every conversation:

- Allergies. Peanut, tree nut, shellfish, egg, soy, wheat, sesame, dairy. Severity matters too — anaphylaxis-grade vs. mild reaction shapes how strict the avoidance has to be on cross-contamination risk. - Intolerances. Lactose, fructose, FODMAPs, gluten sensitivity (distinct from celiac, which is stricter). These don't risk an EpiPen visit but they do ruin a Sunday afternoon. - Religious dietary law. Kosher, halal, Hindu vegetarian (no meat or eggs, dairy ok), Jain (further restrictions), Buddhist fasting practices, Lent, Ramadan timing. Each tradition has variations by family and observance level — Sage tracks the family's actual practice, not a generic textbook version. - Medical restrictions. Doctor-prescribed avoidances — warfarin and high-vitamin-K greens, GERD triggers, low-sodium for hypertension, low-FODMAP for IBS, kidney-friendly potassium limits, diabetes-aware carb pacing. Sage knows because you told her, not because she's reading medical records. - Preferences and dislikes. Mom hates cilantro. Dad doesn't do mushrooms. Your daughter went vegan in college. Your son has been refusing anything green since February. - Kitchen-equipment limitations. No oven (hot plate only). Air fryer is the primary cooking tool. No food processor, immersion blender only. These shape what's actually realistic for your kitchen. - Family member-specific. Most importantly, all of the above is tied to specific family members — not just to the household. So when Sage plans Sunday dinner for your mom visiting, she filters against mom's lactose intolerance. When Sage plans your nephew's birthday dinner, she filters against his peanut allergy. The household-level overlay applies when everyone's eating together.

What Sage does NOT store

This part is non-negotiable. If you are reading this and quietly wondering whether Sage is collecting medical records or selling preferences to advertisers, the answer is no.

Specifically:

- Sage does not store medical records. Sage knows your dad is on warfarin because you told her, in a chat, in your own words. She is not pulling from his EHR. She is not connected to his pharmacy. She has no idea what his INR was last Tuesday. She knows what you told her, and she knows to avoid spinach salads on his nights at your house. - Sage does not share data with anyone. Your family's dietary profile is yours. We don't sell it. We don't license it. We don't anonymize and bundle it and ship it off to a "cooking insights" startup. The thing you taught Sage stays in your account. - Sage does not sell to advertisers. No ad targeting based on what you cook. No third-party analytics looking at your dietary profile. We don't run ads in the product, period. - You can delete it. Anything Sage has learned about your family can be deleted by you, at any time, in your account settings. The memory layer is yours to edit. - Sage is not a substitute for medical advice. This one matters most. Sage will avoid spinach in dad's meal plan because you told her about the warfarin. She is not your dad's cardiologist. She is not telling you it's safe to eat the meal she suggested. The doctor is in charge of the medical side. Sage is in charge of remembering the constraint so dinner doesn't fight with it.

The privacy boundary is built in because cooking for a family is intimate data. Diet says a lot about religion, health, parenting choices, money. We treat it that way.

Real examples (the proof points)

Abstract claims are easy. Here are concrete ones, drawn from how families actually use Sage day to day.

Mom is lactose intolerant. Sage proposed lasagna for Sunday dinner — with cashew bechamel, not cream. The first time, you explain that mom can't do dairy. The next time you say "I want to do lasagna for Sunday," Sage doesn't ask whether mom is coming. She defaults to a dairy-free version because mom's profile is loaded. If you want the regular version because mom isn't visiting that week, you say so and Sage adapts.

My nephew has a peanut allergy. Six weeks after I told Sage, she suggested pad thai — with sunbutter, no peanuts. The instinct is to think Sage would just refuse to suggest pad thai at all. But the better answer is the one she gave: a workable substitute that respects the dish and respects the constraint. Cooking for someone with allergies should not mean a smaller life. It should mean a smarter cook.

Grandma keeps kosher. Sage built a Hanukkah menu and never once suggested mixing meat and dairy. This sounds basic until you've watched a generic AI recommend brisket with cream sauce and feel the small heartbreak of explaining, again, that the family doesn't do that. Sage's memory of the household's kosher observance carries into every menu — including the holiday ones, which is when it matters most.

Dad is on warfarin and avoids high-vitamin-K greens. Sage knows. Spinach salads stopped appearing. Warfarin's interaction with leafy greens is real and well-documented in clinical care. Sage's job here is small but consequential: when she plans a salad night, she defaults to romaine, butter lettuce, or arugula instead of spinach or kale. She knows because we told her, not because she's reading dad's medical records. The doctor still owns the medical side. Sage just owns the cooking-around-it.

We have a kid going through a "nothing green" phase. Sage planned around it without making a thing of it. The non-negotiable trick of feeding a six-year-old is that you don't make the food into a fight. Sage doesn't either. Meal plans for the family stop featuring visible greens for that kid. Hidden ones — carrots in the meatloaf, zucchini in the muffins — stay in. The kid eats. Nobody negotiates at the table. The phase ends in its own time.

My partner has GERD; tomato sauce nights got rough. Once you tell Sage, she shifts your weeknight Italian rotation toward white sauces, pesto, and roasted-vegetable-and-cheese variations. Same cuisine, different acid profile. You didn't have to abandon Italian. You just had to teach Sage once.

Grandpa cooks on a hot plate now. Casseroles became one-pan stovetop meals. Equipment limits are dietary needs in a different costume. When grandpa moved to a smaller place with a single-burner setup, we told Sage. She stopped suggesting anything that needed an oven. The recipes shifted toward skillet meals, no-oven desserts, and stovetop variations of the dishes he'd cooked his whole life.

These are not impressive AI feats. They are exactly the opposite — they are unimpressive in the best possible way. Sage isn't doing anything magical. She is just being a tool that remembers, instead of one that forgets.

Multi-person dietary planning

The hardest part of cooking for a family is not any single restriction. It is layering all of them at the same dinner.

Mom is lactose intolerant. Your nephew has a peanut allergy. Dad avoids high-vitamin-K greens. Your six-year-old is in his "nothing green" phase. Sunday dinner has to feed all four of them. What do you make?

This is where memory turns into actual help. Sage doesn't need to ask what everyone's needs are because she has been told already. She layers all of them automatically when she generates the meal plan. The Sunday-dinner prompt is no longer a constraint-juggling exercise; it's a question of what you, the cook, want to make.

Practically: a roast chicken with mashed potatoes (no butter — olive oil), roasted carrots and parsnips (passes for the kid because they're not green), a vinaigrette-dressed romaine salad (no peanut oil, no spinach), and a fruit cobbler for dessert. That meal works for everyone. Sage assembled it because she had the four constraints already.

The cooking labor doesn't go down. The cognitive labor does. You are no longer the persistent memory layer. You can focus on the actual cooking.

This is what AI is supposed to do. Not write your messages or impersonate your voice. Carry the weight of the boring, persistent, high-stakes details so the human can do the warm, creative, present-moment parts.

Trying Sage today

Anyone can try Sage right now, anonymously, no login required. Open oldfamilyrecipe.com/save-a-recipe and chat with her. Mention an allergy, ask for a meal plan, see what comes back.

The anonymous version is great for kicking the tires. What it can't do is remember you between sessions, because there is no account to attach the memory to. Anonymous Sage is a try-before-you-buy. Logged-in Sage is the version with the persistent memory layer — the version that will still know about your nephew's peanut allergy six weeks from now.

Premium unlocks the full picture: full meal planning, the family cookbook integration, multi-member dietary profiles, and persistent memory that carries across every conversation forever.

That last word matters. Forever. Not "until your trial ends." Not "until you hit a context limit." Not "until the session resets." For as long as you keep your account, Sage remembers. That is the product.

The "forever cookbook" connection

Here's the part that connects this to everything else Old Family Recipe does.

OFR's whole thesis is preservation. The handwritten recipe card from grandma that fades. The family stories that go with the dishes. The Sunday dinner that has to be rebuilt from scratch every generation because nobody wrote it down.

Memory is what preservation is made of. A printed cookbook preserves the recipes. A persistent memory layer preserves the practice of cooking for your family — who can eat what, what mom always wanted on Sunday, what dad won't touch, what the kids actually eat without a fight.

What Sage learns about your family becomes part of your forever cookbook. When you eventually print the family cookbook (we make those — softcover, hardcover, photo-grade heirloom, printed in North Carolina), the recipes inside it have already been adapted to your family's actual needs over months of cooking. The lasagna in the book is mom's lactose-intolerant version because that's the version your family makes. The pad thai is sunbutter pad thai because that's the version your nephew eats. The Sunday dinner section is the dinner that actually got made, week after week, the way your family actually ate.

Memory plus preservation is the whole product. The AI is the memory part. The cookbook is the preservation part. Together they are what we mean when we say "the family cookbook that grows with your family."

A note on what Sage is not

Sage is not magic. Sage forgets sometimes. Sage gets things wrong. The differentiator is not perfect intelligence — it is persistent memory across sessions.

Specifically, you should know:

- Sage will occasionally suggest something she shouldn't. If you have a critical allergy in the house, double-check the recipe she gives you. Memory is not a replacement for reading the ingredient list. Sage is a fast first pass, not the last line of defense. - Sage's memory has to be told things. She doesn't infer your dietary needs from your zip code or read your medical history. She knows what you tell her in chat. The first session has more typing than the tenth session for that reason. - Sage is not a doctor, dietitian, or allergist. For a real medical question — drug interactions, infant feeding, an evolving allergy — talk to the actual professional. Sage's job is to remember what they told you so you don't have to retype it into ChatGPT every Tuesday. - You can correct her. If Sage gets something wrong, tell her. The correction goes into the memory layer too. Over time, she gets more accurate, not less.

The honest version of "AI assistant with persistent memory" is one that is transparent about both halves of the phrase. Memory: yes, real, it persists. Assistant: yes, real, but human-supervised, especially on anything with stakes.

Start here

If your family has any real dietary complexity — allergies, intolerances, religious dietary law, medical restrictions, preferences that have to be respected — Sage is built for you.

- Try Sage right now (no login, free) — chat with her, ask for a meal plan, see how she handles a constraint - Upgrade for full memory and meal planner — the version where she remembers your family across every session, forever - Print the family cookbook — once Sage has helped you build the family's recipe collection, the printed cookbook is the heirloom version

If gluten is the constraint in your house, the most concrete head start is our Gluten-Free Family Starter pack — ten naturally-GF family recipes you can add to your cookbook with one click. No substitutes, no apology copy, no "use this brand of flour blend." Just dishes that were always GF and always will be — a useful scaffold for the cousin who got diagnosed last year and is still figuring out what they can eat at the table.

Cooking for your family is one of the longest-running conversations of your life. The tool you use should remember the conversation.

Sage does. That's the whole pitch.

— Andy Old Family Recipe hello@oldfamilyrecipe.com