Your whole collection.
One AI that works across all of it.
Cook Editor is a free desktop app for your .cook files. CookBot — the built-in AI — imports recipes, plans a week of meals, and edits across your whole library, not one recipe at a time.
Write in plain Cooklang
Syntax highlighting, inline validation, and autocomplete for ingredients
and cookware. Your recipes stay as .cook text files —
diffable, git-friendly, future-proof.
Beautiful preview. Shopping list included.
One click turns your .cook file into a scaled, chip-tagged recipe view.
Select multiple recipes and Cook Editor builds a combined shopping list,
grouped by aisle.
Meal plans in a single file
.menu files link recipes across days and meals. Scale by household size,
see the week at a glance, and let the shopping list flow from the plan.
servings: 2
time: 25 min
Preheat the #oven{180°C}
Mix @flour{200%g} with
@eggs{3} and
@whole milk{250%ml}.
Bake for ~{25%minutes}.
Plain text files. Yours forever.
Every recipe and menu is a text file on your disk. No database. No lock-in. Readable in any editor in fifty years.
Built to be extended.
Cook Editor runs on the VS Code extension engine — so it bends to how you work.
Plugins
Cook Editor runs VS Code extensions. We’ve just opened a plugin marketplace — install community plugins in a click, or build your own with the VS Code Extension API you already know. It’s early days, and we’re looking for the first authors.
Custom reports, your way
Render any recipe or menu through your own Jinja templates — shopping lists, cost breakdowns, recipe cards, nutrition sheets, CSV or HTML exports. Right-click a .cook file, pick a template, and it renders in a new tab.
CookBot, built in
The AI assistant lives in a sidebar. It can pull in recipes and menus from your collection to answer questions, import recipes from URLs, and draft meal plans — writing changes directly to your files with your approval. Included with Cookbot Pro.
- Your files stay on your disk. CookBot only reads what you choose to share in the conversation — never your full collection.
- Every change is a diff you approve. Nothing is written to disk until you click accept.
- Open source. The editor and the CookBot integration are public on GitHub — inspect how prompts and files are handled.
Edit on your laptop.
Cook from your phone.
Cook Editor plays nicely with the Cooklang apps for iPhone and Android. Your collection and shopping list stay in sync, so you can tick items off at the store while someone else preps at home.
Simple pricing.
Cook Editor
- The editor & mobile apps — free
- Recipe preview and scaling
- Shopping lists by aisle
-
.menumeal plans - Works with iOS & Android apps
Cookbot Pro
Cancel anytime. Pay monthly — no annual lock-in.
- Everything in Cook Editor
- Unlimited CookBot AI conversations
- Recipe import from any URL
- AI meal planning
- Meal plans across your whole library
Cancel anytime
Things people ask before signing up
Where do my recipes go when I use CookBot?
.cook files stay on your local disk. CookBot is powered by Anthropic's Claude Sonnet: when you ask a question, only the specific file content you reference is sent to Anthropic for processing — never your full collection. Cook MD doesn't store conversations on our servers, and Anthropic doesn't train on API data. Every change CookBot suggests is shown as a diff and only written to disk after you accept it.
Can I cancel anytime?
How do I pay? Which cards work?
Why a subscription for a desktop app?
What happens to my recipes if I stop paying?
.cook and .menu files are plain text on your disk — they keep working in any text editor, in Cook Editor itself, and on the mobile apps. You only lose the CookBot AI features.