Overview

Recipes define which providers, secrets, profiles, and proxy configuration are deployed to ~/.codefreedom. Each recipe extends _default (shared tool profiles, base proxy config) and layers its own providers on top.

Available Recipes

costeffective-coding

Cloud-only inference. Routes through Azure Foundry, OpenCode Zen, and OpenRouter via the LiteLLM proxy.

Required secrets: LITELLM_MASTER_KEY, MICROSOFT_FOUNDRY_API_KEY, OPENCODE_ZEN_API_KEY, OPENROUTER_API_KEY, GITHUB_PERSONAL_ACCESS_TOKEN

Providers: Azure Foundry (GPT-5.x), OpenCode Zen (MiMo, DeepSeek, Qwen — free + subscription), OpenRouter (DeepSeek, MiMo, Qwen, MiniMax, Kimi, FreeRouter)

Full documentation →

costeffective-coding-with-local

Cloud + local inference. Everything in costeffective-coding, plus local Qwen model backends.

Additional secrets: LOCAL_M_API_KEY, LOCAL_S_API_KEY

Additional providers: Local Qwen3.6-27B and Qwen3.6-35B-A3B via OpenAI-compatible servers

Full documentation →

Apply a Recipe

cf setup init --plan-and-apply <recipe-name>

Short alias:

cf s i -pa <recipe-name>

Example:

cf s i -pa costeffective-coding

What Happens

1. CodeFreedom clones the recipe from the remote store
2. Generates a plan showing which files will be created, replaced, or left unchanged
3. Applies the plan after confirmation
4. Reports which secrets are set and which are missing

After Applying

Run the setup script to configure your API keys:

bash ~/.codefreedom/scripts/<recipe-name>/setup-secrets.sh

The script sets CF_CLI_* machine environment variables, persists them in your shell profile, and reports which services are configured.

Recipe Inheritance

Both recipes extend _default, which provides:

• Shared tool profiles (Chrome, Web, GitHub, Web Bridge)
• Base proxy Docker Compose configuration
• Base LiteLLM proxy config
• Reasoning efforts plugin mapping

When you switch recipes, shared files are merged (deepdiff) so your customizations are preserved. Only recipe-specific files (providers, secrets) are replaced.