cook.md

Plugins

Plugins add features to Cook Editor — new panels, buttons in the recipe preview, commands, even new file types. Cook Editor runs the same kind of extensions as VS Code, plus a small Cooklang API, so a plugin can work with your recipes the way the built-in features do.

Installing and turning plugins off

Open the Extensions view from the activity bar on the left. It searches plugins.cook.md, the Cook plugin marketplace. Click Install on a plugin and it's active straight away.

To turn a plugin off, find it under Installed and choose Disable. Its buttons and panels disappear; your files are untouched. Uninstall removes it completely.

Extensions view listing installed plugins: Allergens, Cookbook, Core Vitals, Diet Badges, Macros, Meal Journal, Nutri-Score, Pantry, Pantry Match and Recipe Hub

Plugins that come with Cook Editor

  • Shopping List — builds an aisle-grouped shopping list from recipes and menus, subtracting what's in your pantry.

Default plugins are ordinary plugins: you can disable them like any other, and they're built with exactly the same API third-party plugins use.

Our other plugins are optional; install them from the Extensions view. For example, Pantry shows what's in your pantry, what's running low and what expires soon, and lets you edit it without touching the file.

Recipe preview with badges from optional plugins: allergens, Core Vitals, diet, macros, Nutri-Score and pantry match

Optional plugins at work in a recipe preview: the Allergens, Core Vitals, Diet Badges, Macros, Nutri-Score and Pantry Match badges sit next to Scale.

Building your own

If you know a little TypeScript you can write a plugin in an afternoon. The step-by-step tutorial takes you from an empty folder to a published plugin. Then see the Cooklang API and the outlets where plugins can add buttons. When it's ready, publish it to plugins.cook.md.