[FEATURE] remote-control CLI should support worktree arguments

Problem Statement

claude remote-control <name> doesn't support worktree flags, so you can't start a remote-control session in a worktree from the CLI. You must instead start claude in a worktree directory interactively and then use /remote-control "name".

Proposed Solution

1. Add --worktree / -w flag to claude remote-control so it can create/enter a worktree and start the remote-control session in one command. The provided name is reused as the worktree name — e.g. claude remote-control "name" --worktree creates a worktree called "name" and starts a remote-control session called "name".
2. Support --remote-control / -r flag on claude -w <name> as the inverse — e.g. claude -w "name" --remote-control creates a worktree called "name" and starts a remote-control session called "name".

In both cases, the single provided name serves as both the worktree name and the remote-control session name. --worktree/-w and --remote-control/-r are complementary flags that can be combined from either direction.

Alternative Solutions

Current workaround is to cd into a worktree, start claude interactively, then run /remote-control "name".

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case

Starting a remote-control session in a worktree from a script or one-liner without interactive steps.