Recipes

A recipe is a saved, reusable query with options, such as "monthly revenue by country, for a chosen year". Run it on the canvas and its answer lands as a result table in your model; run it again and the same table is brought up to date.

Recipes give a metric one definition. Instead of five people each writing their own revenue query and getting five slightly different numbers, everyone runs the same recipe, and AI assistants run it too.

How a recipe works

A recipe holds a definition and no data. Each run reads the tables it names and writes its answer into a table in the model you choose:

  • The recipe lives in your organization's catalog, on the Recipes page. It says what it reads, what options it takes, and the SQL it runs.
  • A result is an ordinary-looking table in a model, marked as the recipe's answer. It holds rows and nothing else; its meaning lives in the recipe that made it.

A recipe only ever reads tables you can read. Someone who can't read one of its inputs can't run it.

Create a recipe

Recipes are written by an AI assistant connected through the MCP server. Ask it in plain words, for example "Save a recipe for monthly revenue by country, with the year as an option", and it creates the recipe with create_recipe, or widens an existing one with update_recipe.

There is no recipe editor in the app. An assistant won't create a near-duplicate either: if a recipe already reads the same tables and columns, it extends that one instead, so the catalog keeps one definition per question.

A recipe you create is private: only you see it. Recipes your colleagues published appear to everyone in the organization who can read their inputs.

Find a recipe

Open Recipes in the sidebar. The page has two shelves and a search box:

  • Yours: the recipes you created.
  • Published in this org: the recipes others published for the organization.

Click a recipe to open it. The dialog shows what it computes, its Inputs (the options a run takes), what it Reads, and its SQL, with table and column names as you see them.

Run a recipe

  1. Open the model where the answer should land.
  2. Choose Import → Mycorr on the action bar and find the recipe, by browsing or with the search box.
  3. Drag it onto the canvas. The run dialog opens where you dropped it.
  4. Under Controls, set the options, or leave the defaults.
  5. Under Result, check the Table name, and for a private recipe choose the Version it reads: Latest, the tables as they are now, or Released, their published releases. A published recipe always reads releases.
  6. Click Run.

The dialog closes and the table arrives on the canvas when the run finishes. Running a recipe needs the right to edit the model.

Result tables

A result is easy to spot: its title starts with Σ, and its details panel shows a recipe result chip and a Recipe section with the recipe's name and Open recipe.

  • It is read-only. Nobody edits a result, not even its owner: change the recipe or its options and run it again.
  • A re-run updates it in place. Open recipe reopens the run dialog with the options that made the table. Click Update with the same options and the same table is rewritten with fresh numbers; change an option and the table is replaced with the new answer.
  • Its links are drawn for you. The run works out how the result relates to the tables it read, and links it to them. You can't draw or delete a result's links by hand.
  • It can't be shared, imported elsewhere, checkpointed or added to a dataset. The recipe is what you share; anyone who can read its inputs can run it into their own model.
  • It can be deleted without the Trash. Because the recipe can rebuild it, deleting a result removes it for good. It is also the one kind of table an AI assistant may delete, and only for someone who collaborates on or manages the model's space.

When a recipe can't run

A recipe depends on the tables and columns it reads. If one of them is deleted, the recipe stops running rather than computing over data you believe is gone:

  • If the column is only soft-deleted, restore it in the app and the recipe runs again.
  • If it is gone for good, the recipe needs a new definition. Ask your assistant to update it.

The dialog says why a recipe can't run, for example "This recipe cannot run" or "This recipe cannot run from the app yet" for a recipe whose options the app can't show.

Delete or deprecate a recipe

Open the recipe from the Recipes page. Under Manage:

  • A private recipe has Delete recipe. It removes the recipe and every result table it made, so the dialog tells you how many go with it. This can't be undone.
  • A published recipe can't be deleted, because other people's results depend on it. Deprecate marks it so nobody builds new results on it, while existing results keep re-running. Undeprecate reverses it.

Only the recipe's author can delete or deprecate it.