[DOCS] Remote Control docs are outdated for server mode, resumable sessions, and explicit naming syntax

[coygeek]

Documentation Type

Incorrect/outdated documentation

Documentation Location

https://code.claude.com/docs/en/remote-control

Section/Topic

Remote Control startup/limitations sections and related CLI command coverage for server mode, session persistence, and naming syntax.

Current Documentation

The docs currently say:

The process stays running in your terminal, waiting for remote connections.

Use /rename before running /remote-control to give the session a descriptive name.

Terminal must stay open: Remote Control runs as a local process. If you close the terminal or stop the claude process, the session ends.

Extended network outage: ... the session times out and the process exits.

And CLI reference currently lists:

| claude remote-control | Start a Remote Control session ... |

What's Wrong or Missing?

A. Missing claude remote-control server documentation

Changelog v2.1.64 adds claude remote-control server for hosting multiple concurrent sessions with worktree or same-dir isolation, but the Remote Control docs only describe single-session claude remote-control / /remote-control flows.

B. Session persistence behavior is outdated

Changelog v2.1.64 adds persistent session support with session_key that survives WebSocket disconnects and can resume across server restarts, with new --workspace, --idle-timeout, and --max-sessions flags. Current limitations still describe sessions as ending after terminal close/outage with no resumable server guidance.

C. Explicit naming syntax is missing

Changelog v2.1.64 adds optional naming syntax (/remote-control My Project and claude remote-control --name "My Project"), but docs only recommend running /rename first.

Suggested Improvement

Add a dedicated "Remote Control server mode" section that covers:

1. claude remote-control server purpose and isolation modes.
2. Session persistence model (session_key), reconnect behavior, and restart semantics.
3. New server flags (--workspace, --idle-timeout, --max-sessions) with examples.
4. Explicit naming examples for both slash command and CLI --name argument.
5. Updated limitations text distinguishing ephemeral single-session mode vs resumable server mode.

Impact

High - Prevents users from using a feature

Additional Context

Affected Pages:

Page	Line(s)	Context
https://code.claude.com/docs/en/remote-control	42-50, 63, 101-102	Only documents claude remote-control//remote-control, recommends /rename, and describes non-resumable session limitations
https://code.claude.com/docs/en/cli-reference	28	Lists claude remote-control only; no claude remote-control server entry
https://code.claude.com/docs/en/interactive-mode	137-139	Shows /remote-control and /rename, but no inline name argument syntax for /remote-control

Total scope: 3 pages affected

Source: Changelog v2.1.64

• Added persistent session support to claude server ... New flags: --workspace, --idle-timeout, --max-sessions.
• Added claude remote-control server for hosting multiple concurrent sessions with worktree or same-dir isolation.
• Added optional name argument to /remote-control and claude remote-control ... to set a custom session title.

[JJC1138]

Oddly, the 2.1.64 release notes have been removed, so perhaps that feature has been rolled back for now?

When I try to run claude remote-control server I get:

Error: The Remote Control server feature is not enabled for your account yet.

[coygeek]

Issue #30570 Verification

Title: [DOCS] Remote Control docs are outdated for server mode, resumable sessions, and explicit naming syntax
Issue Date: 2026-03-04
Verification Date: 2026-03-18
Status: RESOLVED

---

Issue Summary

This issue reports that the Remote Control documentation was missing coverage of: (A) claude remote-control server mode for hosting multiple concurrent sessions, (B) session persistence/resumability, and (C) explicit naming syntax via --name flag and inline arguments to --remote-control and /remote-control.

---

Verification Results

Claim A: Missing claude remote-control server documentation

Status: RESOLVED

The Remote Control page at https://code.claude.com/docs/en/remote-control now documents server mode prominently under the "Start a Remote Control session" section in a tabbed layout. The "Server mode" tab documents claude remote-control running in server mode with a full flags table including:

• --spawn <mode> with same-dir (default) and worktree isolation modes
• --capacity <N> for maximum concurrent sessions (default 32)
• --verbose for detailed connection and session logs
• --name "My Project" for custom session titles

The description explicitly states: "The process stays running in your terminal in server mode, waiting for remote connections."

Verdict: Server mode with concurrent session support is now fully documented.

Claim B: Session persistence behavior is outdated

Status: RESOLVED

The documentation has been updated to reflect the current session model. The Limitations section now states:

"One remote session per interactive process: outside of server mode, each Claude Code instance supports one remote session at a time. Use server mode with --spawn to run multiple concurrent sessions from a single process."

The "Enable Remote Control for all sessions" section also explains: "If you run multiple instances, each one gets its own environment and session. To run multiple concurrent sessions from a single process, use server mode with --spawn instead."

The old limitations text about sessions ending after terminal close has been updated while retaining accurate warnings about process termination.

Verdict: The limitations and session behavior sections now distinguish between single-session interactive mode and multi-session server mode.

Claim C: Explicit naming syntax is missing

Status: RESOLVED

The documentation now shows explicit naming syntax in three places:

1. Server mode tab: --name "My Project" flag in the flags table
2. Interactive session tab: claude --remote-control "My Project" example with description "Optionally pass a name for the session"
3. Existing session tab: /remote-control My Project example with description "Pass a name as an argument to set a custom session title"

The old recommendation to use /rename before /remote-control has been replaced with direct inline naming examples.

Verdict: All three naming syntax variants are now documented with examples.

---

Current State

Claim	Status
Missing server mode documentation	RESOLVED
Outdated session persistence behavior	RESOLVED
Missing explicit naming syntax	RESOLVED

---

References

• https://code.claude.com/docs/en/remote-control

---

Conclusion & Recommendation

Primary Concern: Remote Control docs were missing server mode, session persistence, and naming syntax introduced in v2.1.64.

Resolution Status: RESOLVED

Recommendation: CLOSE

The Remote Control page has been substantially rewritten with a tabbed layout covering server mode (with --spawn, --capacity, --verbose flags), interactive session mode, and existing session mode. All three naming syntax variants are documented with examples. The limitations section has been updated to distinguish between single-session and multi-session modes.

[github-actions]

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.