Rescue

Fix the dish you already started.

Rescue is built for the exact moment a recipe goes sideways. Instead of generating a new meal idea, it reads the problem you describe and returns a short rescue plan with likely causes, simple corrective steps, and a quick safety note.

This works best for issues like undercooked chicken, oversalted soup, bland sauce, dry meat, broken gravy, watery curry, mushy pasta, or a pan that got too hot too fast. Keep the input specific and the response stays useful.

Use it when: the meal is already cooking, resting, or finished and needs a save.

Describe the problem clearly: what the dish is, what went wrong, and what has happened so far.

Keep it practical: short rescue output, minimal tokens, and no unnecessary recipe rewrite.

Describe what went wrong

Include the dish, the problem, and what you have already tried. Good input gives a tighter fix. Example: "I baked chicken thighs for 25 minutes and the outside looks done, but the center near the bone is still pink. I already covered it with foil."

What happened in your recipe?

Optional: add a photo of the problem

Helpful for color, texture, doneness, burning, splitting, or thickness issues. JPG, PNG, or WebP under 4 MB.

3 of 3 fixes remaining today 0 characters

Need a new recipe instead?

Need a cooking reset before you rescue it?

Browse Cooking Tips & FAQ for quick answers on doneness, storage, substitutions, seasoning, and fix-it basics.

What to include

Name the dish, the symptom, what step you are on, and what ingredients or tools you still have available. That usually gives enough context for a practical save.

What this will not do

This page is not designed to generate a full new recipe. It is for salvage advice, small corrections, and safety-minded next actions.

Why recipes go wrong in real kitchens

Cooking problems usually come from a small number of causes: heat that is too high or too low, moisture leaving faster than expected, pan crowding, a reduction going too far, not enough resting time, or ingredient differences that change timing. A chicken thigh from one pack may finish differently from another; a watery vegetable can thin a sauce; a small pan can steam food that was supposed to brown.

That is why this page asks for concrete context instead of generic keywords. "Undercooked chicken" is not enough by itself. "Bone-in chicken thighs, roasted at 425, outside browned, inside still pink near the bone after 25 minutes" is enough for targeted advice.

Safety matters first

If a fix involves meat, seafood, dairy-heavy sauces, or food that sat out too long, the rescue plan should prioritize food safety before flavor or texture. Some dishes are salvageable; some are not worth the risk.

Most fixes are incremental

Strong recoveries come from small corrections: lower the heat, add a little liquid, separate a broken sauce, dilute salt in stages, or finish covered for a short interval. Large swings usually make the problem worse.

Better input gives better rescue

Mention time, temperature, cooking method, and what has already been added. That lets the rescue assistant explain what likely happened and what exact next move gives the best chance of saving the dish.