Cook MD

Features

A tour of everything Cook Editor does, organised by what you're trying to get done.

Writing .cook files

The text editor understands Cooklang natively. Syntax highlighting colours ingredients, cookware, and timers differently from prose. Inline validation flags malformed quantities (@flour{200grams}) and unmatched braces before you hit save. Autocomplete suggests ingredients and cookware you've used in other recipes, so your collection stays consistent over time.

Metadata lives in YAML frontmatter at the top of the file — servings, time, tags, anything you want. The preview and shopping list read from that block.

Preview & scaling

The preview pane renders a .cook file as a clean recipe card — numbered steps, ingredient chips, timers, cookware pulled into their own sections. Toggle it with the split-pane icon in the top right.

The servings control in the preview scales every quantity in the recipe, including anything you've written with fractions (1/2) or mixed units. The original file is not modified — scaling lives in the preview.

Shopping lists

Select one or more recipes in the sidebar and open the Shopping panel. Cook Editor merges their ingredient lists, combines duplicates (@flour{200%g} + @flour{150%g} becomes 350 g), and groups the result by aisle — produce, dairy, pantry, and so on.

The list is reactive: tick an item to cross it out, add or remove recipes from the selection and the list updates. Via the Cook.md sync, the same list appears on the mobile apps, so you can cook together and still share one list.

CookBot AI sidebarCookbot Pro

CookBot is an AI assistant that lives in a sidebar inside Cook Editor. Ask it a question and it can pull in specific recipes or menus from your collection to answer in context ("what's planned for this week?"), import recipes from any URL into a clean .cook file, and draft new recipes or meal plans.

Every change CookBot wants to make — creating a file, editing a recipe, writing a menu — is shown as a diff first. Nothing lands on disk without your approval.

CookBot is included with a Cookbot Pro subscription. Without a subscription, the rest of Cook Editor still works as a full editor and preview — CookBot is a Pro-only sidebar.

CookBot data & privacy

CookBot is built on Anthropic's Claude Sonnet. Here's exactly what happens when you ask it something.

  • Your files stay on your disk. Cook Editor reads from and writes to your local folder. We don't upload your collection.
  • Only the file content you reference is sent. When CookBot needs to look at a recipe or menu to answer your question, it includes that file's contents in the request — not your whole collection.
  • We don't store conversations on our servers. Your messages and the file content they reference are forwarded to Anthropic for processing; the reply comes back to your editor. Cook MD doesn't persist the conversation contents.
  • Anthropic doesn't train on API data. Per Anthropic's commercial terms, content sent through their API is not used to train their models.
  • Every write is a diff you approve. CookBot can propose changes to your files, but nothing is written until you click accept.

Cook Editor is open source, so the exact prompts and tool calls are auditable. If you spot a privacy concern, file an issue on GitHub.

Keyboard shortcuts

Cook Editor is built on the Theia IDE framework, so if you've used VS Code the shortcuts are familiar.

  • Cmd/Ctrl + Shift + P — open the command palette (every action is here).
  • Cmd/Ctrl + P — quick-open a file by name.
  • Cmd/Ctrl + S — save.
  • Cmd/Ctrl + B — toggle the sidebar.
  • Cmd/Ctrl + \ — split the editor.
  • Cmd/Ctrl + Shift + V — open the recipe or menu preview (Cook-specific).

The command palette is the fastest way to find an action you don't remember the shortcut for — start typing and it filters in real time.