What
The claude remote-control command gains a server subcommand that runs as a persistent server accepting multiple concurrent sessions, with isolation and session management options.
Usage
# Each session gets its own git worktree (up to N concurrent)
claude remote-control server --spawn-worktree-sessions [<N>]
# All sessions share the current directory (up to N concurrent)
claude remote-control server --spawn-same-dir-sessions [<N>]Details
--idle-timeout <ms>controls how long detached sessions remain alive (0 = never)--max-sessions <n>caps concurrent sessions (0 = unlimited)--auth-token <token>adds bearer token authentication; auto-generates tokens withsk-ant-cc-prefix if omitted--workspace <dir>sets the default working directory for sessions--host <string>and--port <number>control bind address- Sessions can connect via unix domain sockets using the
cc+unix://protocol - Session lifecycle is tracked in
server-sessions.json - The previous
claude remote-control(withoutserver) for single-session use still works
Evidence
Server session manager (search for "--spawn-worktree-sessions", "server-sessions.json", "sk-ant-cc-")
Strings lifted out of the shipped bundle, so the claim above can be checked against them.