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

Resolved 💬 3 comments Opened Mar 4, 2026 by coygeek Closed Mar 18, 2026

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.

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗