Open Orchestrator

Appearance

The delete command performs a full teardown of a worktree: kills its tmux session, removes the git worktree, and clears status tracking data.

Usage ​

bash
owt delete <name> [OPTIONS]

Alias: owt rm

Arguments ​

ArgumentDescription
nameWorktree name or branch name to delete

Options ​

OptionDescription
-f, --forceForce deletion even with uncommitted changes
-y, --yesSkip confirmation prompt

Examples ​

Basic Deletion ​

bash
owt delete add-auth

Output:

Delete worktree 'add-auth'? [y/N] y
✓ Killed tmux session: owt-add-auth
✓ Removed worktree at /Users/you/projects/my-app-add-auth
✓ Cleared status tracking
✓ Worktree deleted successfully

Skip Confirmation ​

bash
owt delete add-auth --yes

Force Delete with Uncommitted Changes ​

bash
owt delete add-auth --force

Warning: This discards any uncommitted changes in the worktree.

Combine Flags ​

bash
# Force delete without confirmation
owt delete add-auth -f -y

What Gets Deleted ​

When you delete a worktree, Open Orchestrator performs a full teardown:

  1. tmux session -- Killed if it exists
  2. Git worktree -- Directory and git reference removed
  3. Status tracking -- All tracking data cleared

The git branch itself is NOT deleted. Your commits remain in the repository.

Safety Checks ​

Cannot Delete Main Worktree ​

Error: Cannot delete the main worktree

The main worktree is always protected from deletion.

Uncommitted Changes ​

By default, deletion fails if the worktree has uncommitted changes:

Error: Worktree has uncommitted changes. Use --force to override.

Options:

  • Commit or stash your changes first
  • Use --force to discard changes

Recovering After Deletion ​

Git data (commits, branches) are NOT deleted. The branch still exists:

bash
# Check that the branch still exists
git branch -a | grep add-auth

# Recreate the worktree from the existing branch
owt new "continue auth work" --branch feature/add-auth

See Also ​