Skip to content
CookDex docs
You're reading the docs for CookDex v2026.9.1, an earlier release. See this page in the latest docs.

Safety policies

CookDex previews before it changes anything in Mealie. Writing changes takes a deliberate step, and the riskiest options take an owner’s approval.

Most write-capable tasks default to dry_run=true: the run reports what it would change and writes nothing. In the web UI this is Preview Run.

Live runs (dry_run=false) and other dangerous options are blocked unless an owner enables the task policy through PUT /policies or the web UI unlock flow.

The Backup First option is hidden while a task is in dry-run mode, and is off by default. When enabled for a live run, CookDex creates a Mealie backup before the main task starts. To make backups on their own, see mealie-backup.

Cleanup commands and reimport return a nonzero exit status when their reports contain failed operations, including partial failures. The maintenance pipeline stops on a failed cleanup stage unless continue_on_error=true.