Recipe history

Every time you save a change to a recipe’s text, Mirepoix records that version. You can look back through earlier versions, see what changed, and bring an old version back. (A Save to kitchen that changes nothing records nothing, and neither does swapping the photo — a version holds the written recipe, not the picture.)

History starts fresh

Mirepoix changed how it stores recipes, and the old version records didn’t come with it. History begins at that changeover. A version saved before it can’t be viewed and can’t be restored. A recipe you deleted before it has left Recently deleted for good — an old link to that recipe now lands on a plain not-found page. Every recipe you already had opens its history with a single entry from the changeover, credited to nobody and noted History begins here. Everything saved since is recorded the way it always was.

Open the history

Open a recipe, then tap History in the second row of actions below the recipe header. It’s always there — even a recipe you’ve never edited has its first version to show.

The history page lists every recorded version, oldest first. Each row carries:

When it was saved, and who saved it.
What happened — Original for the first version, updated for a save, restored for a restore. A change that came from Mirabel adds · via Mirabel. A change an app or tool made with an agent access token adds · via CLI and the token’s name, like · via CLI (Work laptop), or · via Siri for the Mirepoix iPhone app.
The note, when that version has one.

Tap View to read a version, or Restore to bring it back. ← Back to recipe returns you to the recipe.

See one version

Tap View on a row. Mirepoix renders that whole version — every step and every ingredient — with the differences from the recipe as it stands now marked. Highlighted text is what this version said; struck-through text is what the recipe says now instead. So a step the recipe has gained since shows struck through, and a step it has lost shows highlighted. The title, the tags, and the rest of the recipe’s details sit at the top, marked the same way.

Above the version, a label tells you how far back you’re looking — N edits behind current, or Current version for the newest one. The newest version has nothing to differ from, so it shows without marks. When the version carries a note, it appears just below that label.

Step to the version before or after with the ◄ and ► arrows, or jump straight to one from the dropdown — no need to go back to the list first.

Tap × close to leave the version and return to the recipe.

Restore an earlier version

Tap Restore on a row in the history list, or Restore this version while you’re reading one. Mirepoix writes that version’s exact content back to the recipe, through the same save the editor uses.

Restoring never erases anything. The restored content becomes the newest version, recorded as restored and noted with the date of the version it came from — so a restore can itself be undone by restoring the version before it.

That date reads in your kitchen’s date settings, and follows them if they change later. Some older restores are the exception: their note keeps the date exactly as it was first written.

The newest version offers no Restore. It’s already what the recipe says.

Notes about your changes

A version is recorded with or without a note. You don’t write these notes yourself — Mirepoix adds one when it changes a recipe on your behalf.

When you rename a recipe, any other recipe that mentions it is updated to match, and each of those saves is noted with the old and new title. Renaming or deleting a tag does the same to every recipe carrying it; so does renaming a category, and deleting one moves its recipes to Miscellaneous with a note saying so.

Choosing which ingredient a line means in the recipe editor (see Check ingredients) doesn’t change the recipe’s text, so a save that only does that adds no version.

A change Mirabel makes when you tap one of her offers — tags she adds, or a category she sets — is recorded like any other save and marked via Mirabel, so you can tell her changes from your own. So is the first version of a recipe you saved from one of her drafts. A recipe the Add Recipe sheet read for you without her, and that you saved from the editor, isn’t: its first version reads plain Original. An edit she proposes to a saved recipe is different: you review it and save it yourself in the recipe editor, so it’s recorded as your own updated version. Read, compare, and restore any of them just like any other version.

A change an app or tool made with an agent access token is recorded under the name of the member the token belongs to, and marked with the token:

via CLI (name) — a token created on the Account page, or for a command-line tool you approved. The name is the name the token was connected with: what was typed in Name when the token was created, or what the tool called itself when it was approved.
via Siri — the Mirepoix iPhone app’s token, once the app is out. It shows no name.

The mark stays after the token is revoked or deleted, so you can still tell where a change came from. When a token’s change renames a recipe, the other recipes updated to match are recorded under the member’s name with the usual note about the rename, but without the mark.

Restore or permanently delete a deleted recipe

A deleted recipe isn’t gone for good. At the bottom of the recipe list, Recently deleted lists the recipes you’ve removed since the changeover.

Tap Restore to bring a recipe back. It returns with its text, its whole history, its photo, and its star and pin. Three things don’t come back:

Its place on the Menu. Add it again if you still want it there.
Its weeks on the Menu — the record of which weeks it spent there, which Mirabel’s forgotten-favorites suggestions and the Recipes page’s working set read. Deleting a recipe erases that record, so a restored recipe starts it fresh.
Its sketch. A restored recipe comes back without one, and Mirepoix draws it a new one in its once-a-day catch-up, as Recipes describes.

Tap Delete forever to remove it from Recently deleted and from recipe history, including the versions saved before any rename. Its photo is deleted too. Mirepoix asks you to confirm before deleting it forever; once confirmed, it can’t be undone.

A deleted recipe stays in Recently deleted even after you give a new recipe the same name, and each deletion gets its own row, so Delete forever always reaches it. Restore can’t bring it back while the name is taken: Mirepoix says so, and you can rename the newer recipe first, then restore this one. A recipe deleted before October 5, 2026 still leaves the list once its name is reused.

One exception: a recipe renamed and then deleted before Mirepoix began tracking this may have left the versions saved under its earlier name behind. Restore doesn’t bring those back and Delete forever doesn’t remove them; they stay hidden in Mirepoix’s records until the kitchen is deleted.

A recipe deleted before Mirepoix started keeping photos, stars and pins in Recently deleted comes back without them.