Methodology
Three recipes, one meal, one mind.
Most recipes are written for one dish at a time. Real dinners are three. Cook Stack is the pattern Meshi uses to keep the three from collapsing into the one you remember last.
The problem isn't recipes. It's interruption.
Cooking three things in parallel isn't hard because the recipes are hard. It's hard because every time the oven beeps, you've stopped doing whatever you were doing — and when you come back, you've forgotten which onion was the seared one and which had two more minutes.
This isn't a personal failing. It's a documented cognitive phenomenon. In a series of papers published in Cognitive Science (2002) and Proceedings of CogSci (2004), Altmann and Trafton showed that the cost of an interruption isn't the interruption itself — it's the resumption lag. Without a few seconds to encode where you were before the interruption hit, you come back to your task with a higher error rate and a longer time-to-correct.
A timer that fires without warning is the worst possible interruption: instant, sharp, demanding immediate action, and zero advance notice to bookmark your current task.
What Cook Stack does about it
Timer rail across recipes
Every active timer — from every recipe in the session — sits in a single horizontal rail at the top of the screen. You don't have to switch recipes to know what's running or how long it has left.
3-second pre-alert before every timer fires
Three seconds before any timer reaches zero, its chip in the rail shimmers and plays a soft tone. That window — short, but deliberate — is the interruption lag. It's enough time to mentally bookmark the current step before attention has to shift.
One-tap recipe switching
Tapping a timer chip jumps to the recipe it belongs to, at the step that's about to need you. Your previous recipe's step state is preserved exactly — when you come back, ingredients are still checked off, the timer is where you left it, and the scroll is already on the next instruction.
What this looks like for a Sunday dinner
You've picked three recipes: a slow-roast chicken (90 min), garlic mashed potatoes (25 min), and a salad you'll throw together at the end. Cook Stack lays them on a single timeline so the chicken goes in first and the potatoes start at exactly the right moment to finish together.
As you start the chicken, the rail shows its timer. You move to a different room to set the table; 87 minutes later, the rail shimmers and chirps. By the time the timer fires three seconds after that, you've already mentally let go of the table and walked back to the kitchen. Tap the chip — Cook Stack drops you on the chicken's resting-step. You take it out. Then you switch to the potatoes mid-cook, knowing exactly which step is next, because nothing about the potatoes' state was lost while you were on the chicken.
The whole dinner happens without anything boiling over, without the chicken sitting out while you remember what you were doing, and without you having to mentally context-switch back to where you left off.
Why no other recipe app does this
Single-recipe cook modes are everywhere. They're a solved problem: show the step, run the timer, scroll on completion. The interesting design problem isn't the recipe — it's the cognitive load of cooking two or three at once, which is what real meals usually are. Most apps don't even try.
Cook Stack is the part of Meshi we kept refusing to ship until the interruption-lag pre-alert worked. Without it, parallel cooking is just a checklist with extra steps. With it, the cognitive overhead drops to the actual cooking and nothing else.
Try Meshi free
Cook Stack ships with every Meshi account. No upgrade, no paywall, just the cook mode.
Start cooking