Meals

Your agent plans dinner.
This is where the plan lives.

ChatGPT, Claude or Muse writes the week. Meal Coordinator keeps it — readable on your phone, printable for the fridge, and the same in every chat you open, instead of buried in the one where you asked.

Create an accountSign in

Your own plans, recipes and keys. Nobody else’s.

Tuesday, as your agent wrote it

Dinner

Sheet-pan chicken with lemon and potatoes

Serves 850 min

Doubled this week — the cousins are staying. Two trays.

Ingredients

  • 8 chicken thighs, bone in
  • 1.5 kg small potatoes, halved
  • 2 lemons, 6 cloves garlic, a bunch of thyme

Method

  1. Toss everything with oil and salt across two trays.
  2. Roast at 220°C for 45 minutes, swapping trays halfway.
Was it a winner?

What you get

This week, on one page

Every meal with its full recipe, ready to cook from. Open it on your phone at the shop, or print it: black on white, no clutter, nothing split across a page.

A winners library that stays curated

Only recipes you have cooked and said yes to go in, so it fills with things you actually like rather than everything you ever tried. Every recipe keeps its history, and a deleted one can be put back.

Paste a link, decide after dinner

Drop in a recipe link from a friend or a newsletter. Your agent works it into an upcoming week; afterwards you say yes or no. Yes saves the version you actually cooked. No is remembered, so the same link never comes round again.

Works with the agents you already use

ChatGPT, Claude, Claude Code and Muse connect in about a minute, with a key and a skill file the app hands you ready to use. They all read and write the same plans, so a week planned in one is there in the next.

How a week works

  1. 1

    Ask your agent to plan the week

    In whichever app you already talk to. It knows your winners, the links you’ve pasted, and who is eating.

  2. 2

    It writes the plan here

    One complete copy of each recipe, per day, with the amounts already right for that night. Nothing to scale, nothing to look up.

  3. 3

    Cook, then say which ones were winners

    A check or a cross on each new meal. Winners go into the library as cooked; the rest are remembered so nobody suggests them twice.

Each day is its own copy

A meal on a plan is not a pointer to a recipe. It is a snapshot: the whole recipe, as it should be that night.

  • Double Tuesday because the cousins are staying, or swap chicken for tofu for one week, and only that day changes. The recipe in the library is untouched.
  • Delete a recipe from the library and every past week still reads in full.
  • A week can be printed years later and still be exactly what was cooked, notes and all.

What it doesn’t do

It stores a few things and does them properly. The rest is your agent’s job, and it is better at it.

  • It doesn't plan meals

    Your agent does. This is the shared place the plans go, so they survive the chat that made them.

  • No shopping list of its own

    The agent reads the week’s recipes, combines the ingredients, and orders with whatever tools it has.

  • No recipe forms

    Recipes are plain text, stored exactly as written. “3–4 cloves garlic” stays “3–4 cloves garlic”.

Start with this week

Make an account, connect the agent you already talk to, and ask it what to cook. The plan is here when you get to the kitchen, and on your phone when you are at the shop.

Create an account

Under the hood it is a small REST API with an OpenAPI spec, and the same API over MCP for the clients that speak it. Your recipes are yours: markdown in a database, one account per household, keys you can revoke.