Recipes

What Are Recipes?

Recipes are saved workspace presets that launch multiple panels at once. Each recipe defines a combination of terminals, AI agent sessions, and dev server panels, complete with commands, starting prompts, and environment variables. You can spin up your preferred layout in one click, and every panel runs in the active worktree's directory so agents and terminals always start in the right branch.

A single recipe can open up to 10 panels in any combination. You can launch recipes from the RecipeRunner (the empty state when no panels are open), from the new worktree dialog, or broadcast them to multiple worktrees at once via Bulk Operations.

Recipe Scopes

Recipes exist in three tiers that control where they are available and how they are stored.

Team recipes are not created directly. Instead, you promote a Global or Project recipe to Team status using Save to Repo in the Recipe Manager. This writes the recipe to .daintree/recipes/ where it can be committed and shared via git.

Team recipes take priority over project-local recipes. If a team recipe and a project recipe share the same name, only the team version is shown. New project recipes default to in-repo storage, so they are ready to be committed and shared from the start.

The Recipe Manager

The Recipe Manager is a dedicated dialog for managing all your recipes across all three tiers. Open it from the action palette (Cmd+Shift+P and search for "Recipe Manager").

The dialog shows three labelled sections: Global Recipes, Team Recipes (visible when .daintree/recipes/ contains recipe files), and Project Recipes. Each section header has a "New" button for creating recipes in that tier.

Per-Recipe Actions

Hover over any recipe row to reveal action buttons:

Creating Recipes

Click New Global Recipe or New Project Recipe in the relevant section header. You can also right-click any worktree card and select Save Layout as Recipe to capture all currently active panels, including their agent types, commands, and prompts.

Importing Recipes

The Project Recipes section footer has two import buttons: Import from Clipboard (opens a dialog with a text area and scope selector) and Import from File (opens a file picker for .json files). Import validation checks for required fields and drops any invalid panel definitions rather than rejecting the whole recipe. The import only fails if no valid panels remain after validation.

The Recipe Editor

The recipe editor opens when you create or edit a recipe. It has recipe-level settings at the top and panel definitions below.

Recipe-Level Fields

• Recipe Name — required, auto-focused when the editor opens
• Scope — Global or Project. On edit, this is read-only since scope cannot change after creation
• Show in Empty State — pins the recipe to the Pinned section of the RecipeRunner
• Auto-assign Issue — controls whether the linked GitHub issue is auto-assigned to you when creating a worktree with this recipe. Options: "Always assign to me" (default), "Ask before assigning", "Never assign". See GitHub Integration for issue linking setup

Panel Definitions

Each recipe contains one to ten panels. The available fields depend on the panel type:

Every panel also supports optional environment variables and a custom title for the tab label. All panels run in the active worktree's directory.

Agent Model and Launch Flags

The Arguments field on an agent panel accepts any CLI flags the agent binary supports. Those flags are saved in the recipe file and passed verbatim every time the recipe launches. This is the right place to pin a specific model for a recipe, for example --model claude-opus-4-5 for Claude Code or --yolo for Gemini CLI.

The model you pick inside a running agent session (via the agent's own UI or a slash command) is not part of the recipe file. Saved recipes always launch with your global agent configuration unless you override it through Arguments.

Cloning the Active Layout

When creating a new worktree, the Run Recipe dropdown in the New Worktree dialog offers Clone current layout as its first option. The same option is available when creating worktrees in bulk. Instead of running a saved recipe, it snapshots every active panel in the source worktree and forwards that arrangement to the new one.

The snapshot carries a bit more than a saved recipe does. Alongside the usual panel titles, commands, and prompts, Daintree also forwards the model each agent is currently running with and any launch flags it was started with. The new worktree's agents spawn with the same model selection as the source session, even if that model was chosen mid-session rather than via a recipe.

These live-session values are forwarded only. They are never written to disk, so cloning a layout does not turn into a saved recipe. If you want the same model and flag combination to be reusable, save the layout as a recipe and add the flag to the Arguments field. See Worktrees for the New Worktree dialog and Bulk Operations for the fleet-wide path.

Variables in Prompts

Initial prompts on agent panels support variable replacement using {{double_curly}} syntax. Variables are resolved at run time from the worktree's context and are case-insensitive.

If a variable's context is missing (no issue linked, for example), it resolves to an empty string. Unknown variable names are left unchanged. When both an issue and PR are linked, {{number}} prefers the issue number.

Team Recipes

Team recipes are stored in .daintree/recipes/ inside the repository and committed to git, making them available to everyone working on the project. Each recipe is saved as an individual JSON file, which keeps git diffs clean and minimizes merge conflicts.

Daintree auto-loads any .daintree/recipes/*.json files when a project is opened. New team members get access to shared recipes automatically after pulling. Save to Repo writes directly to .daintree/recipes/ and does not require the "Store settings in repository" toggle to be enabled first.

Saving a Recipe to the Repo

1. Open the Recipe Manager (Cmd+Shift+P and search for "Recipe Manager")
2. Hover over a Global or Project recipe and click Save to Repo
3. Confirm in the dialog. The recipe is written to .daintree/recipes/{recipe-name}.json
4. Choose Delete Original to remove the local copy, or Keep Both to keep it alongside the team version

Environment Variable Handling

When saving a recipe to the repo, Daintree blanks all environment variable values while preserving the keys. This prevents secrets from being committed to git. The keys remain as a signal to teammates about which environment variables need to be filled in locally.

Committing Team Recipes

Daintree writes the recipe file but does not commit it automatically. You need to stage and commit the file yourself.

Export and Import

Exporting Recipes

Recipes can be exported in two ways from the Recipe Manager:

• Export to Clipboard copies the recipe as JSON (without the internal project ID). A checkmark appears for two seconds to confirm the copy.
• Export to File opens a save dialog to write a .json file to disk.

Importing Recipes

The Project Recipes section of the Recipe Manager has two import options:

• Import from Clipboard opens a dialog with a text area for pasting JSON and a scope selector to choose Global or Project.
• Import from File opens a file picker for .json files.

During import, Daintree validates the recipe structure, sanitises control characters from commands and prompts, and drops any panels with invalid types. The import only fails if no valid panels remain after validation.

RecipeRunner (Empty State)

When a worktree has no active panels, the content area shows the RecipeRunner. This is the primary surface for discovering and launching recipes.

Grid Mode and List Mode

With six or fewer recipes, the RecipeRunner uses a grid layout (two columns for one to two recipes, three columns for three to six). When you have more than six recipes, it switches to a compact list mode with a search box that auto-focuses for quick filtering.

In list mode, recipes are grouped into three sections:

• Pinned — recipes with "Show in Empty State" enabled
• Recent — the five most recently used recipes, ranked by frequency and recency
• All — remaining recipes in alphabetical order

Search uses fuzzy matching on recipe names, weighted 70% by name relevance and 30% by usage frequency with a seven-day decay.

Keyboard Shortcuts

Context Menu

Right-click any recipe card or row to access: Run, Edit, Duplicate, Pin to Empty State (or Unpin), and Delete.

Zero-Recipe State

When no recipes exist yet, the RecipeRunner shows a brief description of what recipes do and a Create new recipe button to get started.

Example Recipes