[DOCS] Remote Control docs still describe pre-v2.1.92 session naming and omit `--remote-control-session-name-prefix`

Documentation Type

Incorrect/outdated documentation

Documentation Location

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

Section/Topic

Start a Remote Control session flag documentation and the Connect from another device session-naming rules, plus the related claude remote-control and --remote-control entries in the CLI reference

Current Documentation

No documentation currently exists for --remote-control-session-name-prefix on the Remote Control page or in the CLI reference.

The Remote Control page currently says:

| --name "My Project" | Set a custom session title visible in the session list at claude.ai/code. |

The remote session title is chosen in this order: 1. The name you passed to --name, --remote-control, or /remote-control 2. The title you set with /rename 3. The last meaningful message in existing conversation history 4. Your first prompt once you send one

The CLI reference currently says:

| claude remote-control | Start a Remote Control server to control Claude Code from Claude.ai or the Claude app. Runs in server mode (no local interactive session). See Server mode flags | claude remote-control --name "My Project" |

| --remote-control, --rc | Start an interactive session with Remote Control enabled so you can also control it from claude.ai or the Claude app. Optionally pass a name for the session | claude --remote-control "My Project" |

What's Wrong or Missing?

A. The documented default naming behavior appears outdated

Changelog v2.1.92 says:

Remote Control session names now use your hostname as the default prefix (e.g. myhost-graceful-unicorn), overridable with --remote-control-session-name-prefix

The current Remote Control docs still describe unnamed sessions as deriving their titles from /rename, existing conversation history, or the first prompt. That no longer matches the v2.1.92 naming behavior described in the changelog.

B. The new override flag is undocumented

Neither the Remote Control guide nor the CLI reference documents --remote-control-session-name-prefix, what command surfaces accept it, or how it interacts with explicit names set via --name, claude --remote-control "My Project", or /remote-control My Project.

Without that documentation, users cannot predict how unnamed Remote Control sessions will appear in the claude.ai/code session list or intentionally group sessions by machine when they use Claude Code from multiple hosts.

Suggested Improvement

Update the Remote Control docs to reflect the current naming rules for unnamed sessions:

• explain that Remote Control now uses a hostname-prefixed generated name by default, with an example like myhost-graceful-unicorn
• revise or replace the current "The remote session title is chosen in this order" list if it no longer reflects actual behavior
• document --remote-control-session-name-prefix in both the Remote Control flag table and the CLI reference
• clarify where the flag is supported and how it interacts with explicit names from --name, --remote-control "...", and /rename

A short example showing the default generated name and a custom prefix would make the behavior much easier to understand.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/remote-control | Primary Remote Control guide; currently documents the old automatic title-selection rules and omits the new prefix override flag |
| https://code.claude.com/docs/en/cli-reference | claude remote-control and --remote-control reference entries should document or cross-reference the new naming behavior and --remote-control-session-name-prefix |

Total scope: 2 pages affected

Source: Changelog v2.1.92

Exact changelog entry:

Remote Control session names now use your hostname as the default prefix (e.g. myhost-graceful-unicorn), overridable with --remote-control-session-name-prefix