`sbxm apply`

sbxm apply [<project-id>] [--files [--force]] [--worktrees N]
sbxm apply --files --all [--force]

At least one scope is required. In an interactive terminal, omit the project ID to choose a managed project. In a non-interactive terminal, an explicit project ID is required.

Option	Meaning
--files	Re-place files declared in the global configuration, replacing only destinations that still hold what sbxm placed last
--force	With --files, also replace declared files that were edited inside the sandbox or that sbxm has no record of placing
--all	With --files, place the declared files in every registered project instead of one
--worktrees, -t N	Set the desired managed worktree count to 1–32 without lowering it

Without --force, --files refuses before placing anything when a destination holds content sbxm did not place last, and names every such file. --force without --files is refused.

--all cannot be combined with a project ID or --worktrees. It handles each registered project on its own and continues after a project that cannot be applied. Stopped sandboxes are not started. The result lists every project as applied, unchanged, stopped, not-created, or failed, and the exit status is 1 when any project failed.

The worktree count can increase but not decrease. Removing a worktree is not performed as a side effect because its contents may need preservation.

Adding worktrees first brings the sandbox’s repository up to date with its origin. For a project added with --local, that means the host repository pushes its branches and tags into the sandbox again, so the new worktrees start from what the host has now.