add an option to create a worktree from the CLI

[eylonronen]

Feature Request

Problem

add an option to create a worktree from the CLI

Environment

• Version: 2.23.1
• OS: macOS 26.2 (arm64)

[hayke102]

Shipped in #230 (e7772a5) — will land in the next release.

fleet worktree <branch>

Alias wt. Does what the TUI's w key does, from wherever you already are: creates the worktree, copies .claude/settings.local.json + any copy_files entries, and starts a session in it.

fleet worktree fix-login                      # worktree + session, default agent
fleet worktree fix-login --base develop       # base branch (default: repo's default branch)
fleet worktree fix-login --path ~/code/fleet  # target repo (default: cwd)
fleet worktree fix-login --agent codex        # agent (default: your default_agent)
cd "$(fleet worktree fix-login --no-session)" # worktree only, path on stdout

Flags work on either side of the branch name, so fleet worktree foo --no-session parses the way you'd expect. With --no-session stdout is only the path — every message goes to stderr — so it composes into cd "$(...)".

Two behaviours worth knowing:

• Worktrees always derive from the main clone. Run it from inside myrepo-foo and you get myrepo-bar, not myrepo-foo-bar — same as pressing w on an origin header.
• If the branch already exists, the worktree reuses it and says so, and tells you --base was ignored — because it genuinely is.

Sessions now appear without a restart

Worth calling out since it wasn't in the original request. fleet read its session list from SQLite exactly once, at startup — so a session created from a shell would have sat invisible until you restarted the TUI, which would have made the new command feel broken for exactly the person most likely to use it.

The background worker now picks up sessions created by another fleet process within ~5s, empty sidebar included. It only ever adds: fleet remove from a second terminal still leaves a stale row until restart, unchanged from before. Your cursor stays on whatever row it was on, even when the new session slots in above it.

Thanks for the request, @eylonronen.