Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.64 Home All releases ←olderv2.1.63 v2.1.66newer→
Claude Code v2.1.64

Remote Control Server Mode

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 with sk-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 (without server) 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.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.64 →