Mentu

Install

Install

mentu-recipes is the public runner for file-based agent workflows. It is a single macOS binary. Everything it needs to run a shell recipe is in the binary itself.

Requirements: macOS 13 or later. Provider backends need their own credentials. A source build additionally needs a Swift 6.0 or later toolchain.

Install with one line

curl -fsSL https://get.mentu.ai | sh

Apple Silicon and Intel. The script resolves the latest release tag, downloads the binary for this Mac's CPU, checks it against the checksums.txt published with the release, and moves it into ~/.local/bin. It does not use sudo and it does not edit your shell profile. If ~/.local/bin is not on your PATH it prints the line to add, and it ends by naming the next command.

The script is in the repository, so you can read it before you run it: scripts/install.sh, or curl -fsSL https://get.mentu.ai to print what is being served right now.

Environment variables it honors:

Variable Effect
MENTU_VERSION Install a specific version, for example 0.3.0.
MENTU_INSTALL_DIR Install somewhere other than ~/.local/bin.
MENTU_WITH_SKILLS 1 also registers the Claude Code plugin.

Install with Homebrew

brew install mentu-ai/tap/mentu-recipes-bin

The formula downloads the release binary for your architecture and pins its SHA-256, so Homebrew refuses any download that does not match the published checksum. The binary lands at $(brew --prefix)/bin/mentu-recipes.

Confirm the install:

mentu-recipes --version
mentu-recipes 0.5.0
mentu-recipes adapters
shell	shell	plain_text	ignored	available	explicit
openai	llm-http	openai_sse	native	unavailable	auto
openai-chat	llm-http	openai_sse	native	unavailable	auto
deepseek	llm-http	openai_sse	native	unavailable	auto
ollama	llm-http	openai_sse	native	available	auto
claude	agent-cli	claude_json	native	available	auto
codex	agent-cli	codex_json	folded_into_prompt	available	auto

The fifth column reports what this Mac has: shell is always available, the HTTP backends need a credential, and ollama, claude, and codex show available only when the server or CLI is installed.

Install the signed package

Each release also carries a macOS installer package, mentu-recipes-0.5.0-macos-arm64.pkg, signed with a Developer ID Installer certificate and notarized by Apple. It is Apple Silicon only and installs the binary at /usr/local/bin/mentu-recipes. Two paths install it.

With the Homebrew cask:

brew install --cask mentu-ai/tap/mentu-recipes

The cask pins the SHA-256 of the package. It conflicts with the mentu-recipes-bin formula, since both install a mentu-recipes binary.

The package is also on the release page if you would rather download and open it yourself. macOS checks the signature and the notarization when you open it. The manifest the download page reads is public:

curl -s https://api.mentu.ai/v1/releases/latest
{"artifacts":{"macos-arm64":{"url":"https://github.com/mentu-ai/mentu-recipes/releases/download/v0.5.0/mentu-recipes-0.5.0-macos-arm64.pkg","sha256":"9f07c9238b48834ab6036fa6324408a52f6aabc5a2fba5516d1c6160c61e5972","size_bytes":440179}},"version":"0.5.0"}

Install from a release asset

Release binaries are built by GitHub Actions from the tagged source and published with a build provenance attestation.

curl -sLO https://github.com/mentu-ai/mentu-recipes/releases/download/v0.5.0/mentu-recipes-macos-arm64
curl -sLO https://github.com/mentu-ai/mentu-recipes/releases/download/v0.5.0/checksums.txt

Check the download against the published checksum:

shasum -a 256 -c checksums.txt --ignore-missing
mentu-recipes-macos-arm64: OK

Then make it executable:

chmod +x mentu-recipes-macos-arm64

On Intel, substitute mentu-recipes-macos-x86_64.

A matching checksum says the bytes are the published ones. It says nothing about who published them. Check the attestation before you trust the binary: see Verify a release.

Build from source

git clone https://github.com/mentu-ai/mentu-recipes.git
cd mentu-recipes
swift build
Building for debugging...
[0/7] Write sources
[1/7] Write mentu-recipes-entitlement.plist
[3/7] Write swift-version--58304C5D6DBC2206.txt
[5/34] Compiling MentuRecipesCore Onboarding.swift
...
[31/34] Compiling MentuRecipesCore RecipeDoctor.swift
[32/36] Compiling MentuRecipesCore Verification.swift
[33/36] Compiling MentuRecipesCore WorkspaceBaseline.swift
[34/40] Compiling mentu_recipes main.swift
[35/40] Compiling mentu_recipes Setup.swift
[36/40] Emitting module mentu_recipes
[37/40] Compiling mentu_recipes Version.swift
[37/40] Write Objects.LinkFileList
[38/40] Linking mentu-recipes
[39/40] Applying mentu-recipes
Build complete! (4.30s)

Confirm the build runs:

swift run mentu-recipes adapters
shell	shell	plain_text	ignored	available	explicit
openai	llm-http	openai_sse	native	unavailable	auto
openai-chat	llm-http	openai_sse	native	unavailable	auto
deepseek	llm-http	openai_sse	native	unavailable	auto
ollama	llm-http	openai_sse	native	available	auto
claude	agent-cli	claude_json	native	available	auto
codex	agent-cli	codex_json	folded_into_prompt	available	auto

A source build puts the binary under .build/. Run it through swift run mentu-recipes <command>, or copy .build/debug/mentu-recipes onto your PATH.

The source is published under the Mentu Recipes Source Available License v1.0, which permits personal, internal, educational, and evaluation use. Read LICENSE before redistributing a build.

Give Claude Code the skills

The repository is a Claude Code marketplace. Two commands add the plugin:

claude plugin marketplace add mentu-ai/mentu-recipes
claude plugin install mentu-recipes@mentu

It carries two skills and two commands:

Component What it does
writing-recipes The recipe contract: the write boundary, completion, the checks the runner performs, and what doctor flags.
reading-run-records What a run leaves under .mentu/runs, how to find why a step failed, when to resume or retry.
/mentu-recipes:new Turns a task you describe into a recipe that passes check and doctor.
/mentu-recipes:run Runs a recipe and reports what the record says, not what the step claimed.

The skills cost about 210 tokens per session until one of them fires. Remove them with claude plugin uninstall mentu-recipes@mentu.

What you get

The install gives you the runner and nothing else. mentu-recipes init creates .mentu/recipes and .mentu/prompts in your workspace, both empty. mentu-recipes setup places one example recipe, hello-justifiable, in .mentu/recipes and runs it with the shell backend. The quickstart walks through that.

The source repository carries three runnable demo recipes with real transcripts under examples/. They use the shell backend and need no credentials.

Uninstall

Formula install:

brew uninstall mentu-recipes-bin

Cask install:

brew uninstall --cask mentu-recipes

One-line install:

rm ~/.local/bin/mentu-recipes

Package you opened yourself:

sudo rm /usr/local/bin/mentu-recipes
sudo pkgutil --forget ai.mentu.recipes

Claude Code plugin:

claude plugin uninstall mentu-recipes@mentu
claude plugin marketplace remove mentu

Run records live in .mentu/runs/ inside each workspace you used. Delete those directories to remove them.

© 2026 Mentu.