Skip to main content

Recipes

Save multi-panel workspace presets as recipes that launch terminals, AI agents, and dev servers in one click, kept globally on your machine, shared with your team through the repository, or supplied by a plugin.

Updated
Reviewed

What Are Recipes?

A recipe is a saved workspace preset that launches several panels at once. Each recipe describes a set of terminals, AI agent sessions, and dev server panels, with their commands, starting prompts, and launch arguments. You launch your layout in one click. Every panel runs in the active worktree's directory, so agents and terminals always start in the right branch.

One recipe can open up to 10 panels in any combination. You can run a recipe from:

  • The empty-canvas launcher, the surface shown when a worktree has no open panels.
  • The Recipes submenu on a worktree card, and on the row of a scratch workspace or a project folder that is not a git repository.
  • The toolbar's Launcher, which lists recipes alongside agents and panels, or a recipe you pinned to the toolbar.
  • The Recipe field of the New Worktree dialog. Bulk worktree creation runs the same recipe on every worktree it creates; see Worktrees for that flow.

Launch and share covers each route, and Fleet covers driving the agents once they are running.

Recipe Scopes

Every recipe carries a scope. The scope controls where the recipe is offered, where it is stored, and whether your team gets it. The launcher, the recipe picker and the Settings list print each recipe's scope label.

Scope labelAvailable inStorageShared via git
GlobalEvery project on this machineApp-level configNo
TeamThe current project, for everyone who clones it.daintree/recipes/{name}.jsonYes
PluginWherever the supplying plugin is enabledThe plugin's own definitionNo
Project-wideEvery worktree of the current projectMachine-local project storeNo
Worktree: <name>One worktree onlyMachine-local project storeNo

In practice you choose between two when you create a recipe: the editor's Scope field offers Project (current project only) and Global (all projects). A Global recipe lives in Daintree's own config. A Project recipe is written into the repository at .daintree/recipes/ straight away, so it is ready to commit and share from the start, and it shows up labelled Team. The label describes where the file lives, not what you picked in the dropdown. With no project open, only Global can be saved.

Project-wide and Worktree: <name> are the labels of machine-local project recipes, the kind earlier versions of Daintree stored outside the repository. When a project loads, Daintree promotes each of them into .daintree/recipes/. One stays local only when it can't be promoted: its file name is already taken by a different recipe, or the existing file holds content this version of Daintree can't represent.

Note
Scope is locked after creation. To move a recipe into the repository, use Save as team recipe… in the Recipe Manager. To move it anywhere else, use Copy as JSON and import it again with the scope you want. See per-recipe actions.

Plugin Recipes

Enabled plugins can contribute recipes as another origin. The Recipe Manager groups them under Plugin recipes, badges each one Read-only, and names its supplying plugin. Their panel definitions can't be edited or deleted. Use Save as team recipe… to make an editable copy in the repository, or Duplicate recipe to make an editable Global copy. Plugin recipe IDs include their plugin identity, so matching a team recipe name does not replace the plugin contribution. See project plugin surfaces for using recipes as entry points into a project workflow.

When a name is used twice

A machine-local project recipe that shares a name with a Team recipe is shadowed: the Team version is what runs. Shadowed recipes are not hidden. The Recipe Manager and the Settings list badge them Overridden by team recipe, and the launcher dims the name and adds Runs team recipe to the row, describing the Team recipe's panels rather than its own. Running a shadowed row resolves to the Team recipe it defers to, through the local mirror, so environment variable values you filled in locally are still applied.

Showing shadowed recipes rather than dropping them is deliberate: a recipe silently disappearing after a teammate's commit is harder to diagnose than a dimmed row that names what replaced it. A shadowed recipe is not eligible to be the default worktree recipe. Global and plugin recipes never shadow or get shadowed.

Every source in one list, and the row that says which one won

Working with recipes

  • Create and edit for the manager and the editor, saving or cloning a layout you already have open, setting a project's default, and the variables a recipe can put into a prompt.
  • Launch and share for running one from the empty canvas, a sidebar row, the toolbar or across several worktrees, committing team recipes to the repository, and exporting or importing them.

Scratch Workspaces

Scratch workspaces are a separate workspace type, not a recipe scope. They moved to their own page: Scratch Workspaces. A scratch can still run recipes from its row's Recipes submenu; see running a recipe from a sidebar row.

Example Recipes

Recipe NamePanels
Full Stack DevClaude Code + npm run dev terminal + Dev Server
Code ReviewClaude Code (prompt: "Review the changes on {{branch_name}}") + Codex (prompt: "Check for security issues")
Test & Watchnpm run test:watch terminal + Dev Server
Quick FixClaude Code (prompt: "Fix the failing tests on issue {{issue_number}}")
Tip
Once you have a workspace arranged, open the worktree card's Recipes submenu and choose Save current layout as recipe…. It opens the editor on a draft holding each open panel's type, command and after-exit behavior. Prompts and arguments are not captured, so add them before you save. See saving the current layout.