mentu documentation
Run multi-step agent workflows defined as JSON files. Each step declares where it may write and what must be true when it finishes.
What the runner does
Recipes
Multi-step workflows defined as plain JSON. Sequence, fan out and join, or compose whole recipes as nodes.
Declared write boundaries
A step names the paths it may write. Those get committed when it closes. Everything else is quarantined as a patch.
Deterministic verification
grep assertions, file absence, git cleanliness, and shell commands, checked after the step and recorded against its claim.
Backends
OpenAI, DeepSeek, the Claude and Codex CLIs, a local Ollama server, any OpenAI-compatible host, or a local shell.
Run records
Every run writes run.json, an event log, and the captured output of each step under .mentu/runs.
Resume and retry
Pick a failed run back up from its record. Completed steps are skipped, incomplete branches run again.
Built on
Files, not a service
Recipes and prompts are files in your repository. They diff, review, and version like the rest of your code.
Local by default
Shell recipes need no key and no network. Cloud hooks are opt-in per recipe and off unless you turn them on.
Attested releases
Release binaries are built by GitHub Actions from the tagged source and carry a build provenance attestation.
Get started
brew install mentu-ai/tap/mentu-recipes-binmentu-recipes setup