Remote Control Server Mode#
What's wrong with this entry?
A new server subcommand for claude remote-control that runs as a persistent server accepting multiple concurrent sessions from claude.ai/code.
# Start a server where all sessions share the current directory
claude remote-control server
# Each session gets an isolated git worktree (max N sessions)
claude remote-control server --spawn-worktree-sessions [<N>]
# All sessions share the current directory (default behavior, max N sessions)
claude remote-control server --spawn-same-dir-sessions [<N>]
# Additional server options
claude remote-control server --idle-timeout <ms> # Timeout for detached sessions
claude remote-control server --max-sessions <n> # Max concurrent sessions
claude remote-control server --workspace <dir> # Default working directory
claude remote-control server --auth-token <token> # Bearer token for auth
claude remote-control server --host <string> # Bind address
claude remote-control server --port <number> # Listen port- Runs as a persistent daemon that accepts connections without pre-creating an initial session
- Supports
cc+unix://protocol for Unix domain socket connections - Session management with
server-sessions.jsonpersistence andserver.lockfor single-instance enforcement - Configurable spawn modes: shared directory (default) or isolated git worktrees
- Sessions can be created, attached, detached, and destroyed independently
- Policy-controllable via
allow_remote_controlorganization policy
Remote Control server mode (search for "Start a Claude Code session server", "--spawn-worktree-sessions", "server-sessions.json")
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.