Task templates

Task templates live on your laptop, one JSON file per template in ~/.berth/templates/; the file name is its id. The app's New worktree dialog offers them under Template, and fills in the rest from it.

{
  "name": "Fix a bug",
  "description": "A fresh branch and Claude Code, asked for a failing test first.",
  "box": "devl",
  "location": "cal",
  "agent": "claude",
  "branch": "fix/{{name}}",
  "base": "main",
  "prompt": "Fix this bug: {{issue}}\n\nReproduce it with a failing test first.",
  "variables": [{ "id": "issue", "label": "What's broken", "multiline": true }]
}

• box and location are defaults the dialog starts from.
• {{name}} is the task's name, which is also the worktree's.
• Every other {{var}} in branch or prompt becomes an input; variables gives them labels (label), a default, and makes long ones multiline.
• agent is a preset id, or command runs something else.
• A branch that already exists, locally or on origin, is checked out as it is, so a template can review or continue existing work.

The repository's examples/templates has two to start from: Fix a bug and Review a branch.

Templates or project config?Copy Anchor Link

For saved prompts you send to agents that are already running, use the built-in Prompts library instead.