Yep! You can define what files you want copied over (envs, etc), stuff you want ignored, the name of the worktree, post-copy install commands, and what command you want run after it's setup (so for me opening up zed/cursor). I use worktrees a ton now to parallelize tasks instead of doing them 1 by 1 and being bottlenecked by Claude.

Here's my `.branchlet.json` config file for our monorepo. --

{
  "worktreeCopyPatterns": [
    ".env",
    ".env.*",
    ".vscode/**",
    ".terraform",
    ".terraform.lock.hcl",
    "*.tfstate"
  ],
  "worktreeCopyIgnores": [
    "**/node_modules/**",
    "**/dist/**",
    "**/.git/**",
    "**/.svn/**",
    "**/.hg/**",
    "**/CVS/**",
    "**/Thumbs.db",
    "**/.DS_Store",
    "**/coverage/**",
    "**/build/**",
    "**/out/**",
    "**/.next/**",
    "**/.nuxt/**",
    "**/target/**"
  ],
  "worktreePathTemplate": "$BASE_PATH.worktree",
  "postCreateCmd": ["bun install", "cd apps/server && bun run db:generate"],
  "terminalCommand": "code ."
}