Feature request: Interactive picker should run when `--execute` is specified without a branch name

[gbcreation]

Description

When wt switch is called without a branch name, it opens the interactive picker to browse and select a worktree. However, when --execute / -x is combined with wt switch and no branch name is provided, the picker is not shown. Instead, the command errors out with a missing <BRANCH> argument.

wt switch                    # ✅ opens picker
wt switch -x claude          # ❌ error: missing <BRANCH>
wt switch feat/my -x claude  # ✅ switches and runs claude

Expected behaviour

When -x is provided but no branch name is given, wt switch should open the interactive picker as usual, and run the execute command after the user selects a worktree.

wt switch -x claude   # ✅ opens picker → user selects worktree → claude launches

This would make -x composable with the picker, enabling workflows such as:

wt switch -x claude           # pick a worktree, launch Claude
wt switch -x 'claude --continue'  # pick a worktree, resume Claude session
wt switch -x code             # pick a worktree, open VS Code

It also unlocks cleaner alias definitions:

[aliases]
cc = "wt switch -x 'claude --continue'"

[worktrunk-bot]

Thanks for the suggestion — this composes nicely, and there's no way to do it today.

The block is a clap-level constraint: --execute is declared with requires = "branch" (src/cli/mod.rs:400), so wt switch -x claude is rejected at parse time before any picker code runs. That's also why it can't be worked around with a [aliases] entry — the picker path itself never carries an execute command.

The good news is the plumbing is mostly there. Since the picker and the argument path were unified onto a single SwitchPipeline (#2858), that struct already has an execute / execute_args field — the picker just hard-codes execute: None when it builds the pipeline (src/commands/picker/mod.rs:2183). So a change would slot into roughly three places: relax requires = "branch" on --execute, thread the command from handle_switch_command (the args.branch.is_none() branch that calls handle_picker) into the picker, and pass it through to the SwitchPipeline instead of None.

One design question worth flagging: the picker has --branches, --remotes, and --prs modes, which already conflicts_with --execute. Deciding whether -x should be valid only for the default worktree picker or across those modes too is the main thing to settle before implementing.

I'll leave it for a maintainer to evaluate and prioritize.

[max-sixty]

nice idea! let's implement @worktrunk-bot

[worktrunk-bot]

Implemented in #3394. wt switch -x claude (no branch) now opens the picker and runs the command against the selected worktree.

On the open design question from my earlier comment — whether -x should work only with the default picker or across --branches / --remotes / --prs too — I went with all modes, since every picker mode ends by switching to a worktree and -x just runs after that switch. --create / --base / --clobber still conflict with those flags. Easy to scope back to the default picker if you'd prefer; details in the PR.