Managed worktrees
Every project starts with one managed worktree. The supported count is 1–32.
Attached mode
Section titled “Attached mode”The default registration keeps the first worktree on the repository’s default branch:
sbxm add git@github.com:<owner>/<repository>.gitFor an attached project, additional worktrees created later are detached. The first worktree remains the tracking worktree.
Detached mode
Section titled “Detached mode”Choose an explicit starting branch when you want several independent worktrees:
sbxm add git@github.com:<owner>/<repository>.git \ --detach main --worktrees 3Each managed worktree starts detached from the selected branch. This is useful when multiple agents or tasks need isolated directories.
Add worktrees later
Section titled “Add worktrees later”The count can only increase:
sbxm apply <project-id> --worktrees 4apply refuses a lower number. Removing a worktree can delete whatever is checked out there, so reduction is not a side effect of re-running a command. Destroy the project only when that deletion is intentional.
Protection
Section titled “Protection”Before a rebuild or destroy, sbxm checks dirty files, unpublished commits, repository-level refs, unmanaged worktrees, and active sessions. Save work and resolve the reported condition before retrying. A clean worktree does not by itself make a rebuild safe.