worktree-manager

Cursor worktrees are configured via the .cursor/worktrees.json file, which lets you define custom setup commands, environment variables, and dependency steps for parallel agents. Optional scripts in the .cursor directory automate environment setup across different operating systems.

Git worktree cleanup is managed by adjusting max counts and automatic cleanup behavior in .cursor/worktrees.json. This prevents workspace sprawl by automatically removing stale worktrees after parallel agents finish their tasks.

You can inspect and merge Cursor worktrees by listing active worktrees to review changes, then merging them back to your main branch when ready. The Skill provides clear guidance on tracking and integrating parallel agent modifications.

Yes, per-repo worktree behavior supports custom dependency and environment steps. By defining setup-worktree commands and environment handling in .cursor/worktrees.json, you ensure consistent environment setup for each parallel agent across different operating systems.

Parallel agent worktrees lack environment variables when custom setup steps are not defined. You must configure dependency installation and .env file handling in .cursor/worktrees.json to ensure consistent environment setup across all worktrees.

Yes, worktree-manager applies to scenarios running parallel agents or Best-of-N workflows in Cursor. It ensures predictable environment setup, automated cleanup controls, and consistent worktree management across these parallel execution scenarios.