[DOCS] Remote Control docs omit that renames from claude.ai or mobile sync to the local `--resume` session name

Documentation Type

Missing documentation (feature not documented)

Documentation Location

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

Section/Topic

"Connect from another device" and session naming behavior across Remote Control and local resume flows

Current Documentation

The current Remote Control and session docs say:

* Open claude.ai/code or the Claude app and find the session by name in the session list. In the Claude mobile app, tap Code in the navigation to reach the session list. Remote Control sessions show a computer icon with a green status dot when online. 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. An auto-generated name like myhost-graceful-unicorn, where myhost is your machine's hostname or the prefix you set with --remote-control-session-name-prefix If you didn't set an explicit name, the title updates to reflect your prompt once you send one.

And on the sessions page:

Give sessions descriptive names so they're findable in the session picker and resumable by name. Once a session is named, return to it with claude --resume <name> or /resume <name>.

What's Wrong or Missing?

Changelog v2.1.149 says:

Fixed renaming a Remote Control session from claude.ai or the Claude mobile app not updating the local session name for claude --resume

The docs explain how Remote Control sessions get a visible name in claude.ai/code and the mobile app, and they separately explain that local session names are used by claude --resume <name>. But they never state that renaming a live Remote Control session from the web or mobile surface is supposed to sync that new title back to the local CLI session record.

That leaves an important cross-device behavior undocumented: a user can rename a session away from their terminal and then resume it locally by that updated name. Without that note, remote renames read like UI-only labels rather than a rename that also updates the local session metadata.

Suggested Improvement

Add one explicit note in the Remote Control naming section, for example:

If you rename an active Remote Control session from claude.ai/code or the Claude mobile app, Claude Code syncs that title back to the local session record. After it syncs, you can use the updated name with claude --resume <name> or /resume <name> in the CLI.

Also add a short cross-reference on the sessions page noting that Remote Control session renames stay in sync across local CLI and remote clients.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/remote-control | Documents how Remote Control sessions are named and found from claude.ai/code and the mobile app, but not that remote renames sync back to the local CLI session name |
| https://code.claude.com/docs/en/sessions | Documents named-session resume with claude --resume <name>, but not that a Remote Control rename updates the local resumable name |

Total scope: 2 pages affected

Source: Changelog v2.1.149

Fixed renaming a Remote Control session from claude.ai or the Claude mobile app not updating the local session name for claude --resume