Skip to main content
This guide is for humans who want a clean install and a quick way to verify it actually works.

​
Before you start

Make sure these work first:
You should also know which install path you want:
  • npm install — best for normal users
  • linked local checkout — best for development or rapid iteration

​
Option A — install from npm

Then confirm the plugin is loaded:

​
If you use a plugin allowlist

If your OpenClaw config uses plugins.allow, you may need to explicitly allow recipes. Inspect first:
If needed, update it and restart:

​
Option B — install from a local checkout

Verify:

​
Option C — update an existing linked checkout

If you already have a linked local repo:

​
First commands to run after install

These are the fastest sanity checks:
Then scaffold something small:
Or scaffold a team:

​
Important workflow note after install

Installing ClawRecipes does not automatically mean workflow posting side effects are turned on.

​
What is available after a normal install

After install, you have:
  • workflow runner commands
  • workflow files on disk
  • approval flow support
  • file-first run storage

​
What may still require extra setup

If you want workflows to publish content externally:
  • you should configure the supported outbound.post path, or
  • if you rely on a controller-local custom patch, you must reapply that patch after install/update

​
Plain-English warning

If you have a workflow that should post to X or another external destination, do not assume it will post just because the plugin installed successfully. After install/update, either:
  1. configure the supported outbound posting service, or
  2. tell your assistant to turn workflow posting back on / reapply your local patch
See:

​
Uninstall

​
Troubleshooting

​
openclaw recipes ... commands are missing

Try:

​
Plugin installed but did not load

Check:
  • the plugin appears in openclaw plugins list
  • your allowlist is not blocking recipes
  • you restarted the gateway after install

​
Workflow commands exist, but posting is still off

That is possible and expected. Check whether you are using:
  • the supported outbound.post service path, or
  • a local custom patch that needs to be reapplied after install/update

​
install-skill fails

This command uses ClawHub. Try:
If needed:

​
Quick reference