{"version":"2.1.72","anchor":"remote-control-spawn-mode-overhaul","canonical_anchor":"remote-control-spawn-mode-overhaul","heading":"Remote Control Spawn Mode Overhaul","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.72\/e\/remote-control-spawn-mode-overhaul","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.72","markdown":"### Remote Control Spawn Mode Overhaul\n\n**What**\n\nThe remote control `--spawn-worktree-sessions` and `--spawn-same-dir-sessions` flags are replaced with a unified `--spawn <mode>` flag and a new `--capacity` flag.\n\n**Usage**\n\n`claude remote-control --spawn=worktree --capacity=4 claude remote-control --spawn=same-dir claude remote-control --spawn=session` **Details** - `--spawn` accepts `same-dir` (default), `worktree`, or `session` - `--capacity` sets the max concurrent sessions (not valid with `--spawn=session`, which has fixed capacity 1) - New `--create-session-in-dir` \/ `--no-create-session-in-dir` flag controls whether a session is pre-created in the current directory - Interactive spawn mode picker (`w to toggle spawn mode`) when starting remote control - Spawn mode preference is saved per-project - Falls back to `same-dir` if saved mode is `worktree` but the directory isn't a git repo - Error message updated: \"Error: Multi-session Remote Control is not enabled for your account yet.\" **Evidence** New spawn mode infrastructure (search for `\"spawn mode\"`, `\"--spawn\"`, `\"--capacity\"`)"}