[DOCS] Remote Control docs omit that claude.ai renames persist to the local CLI session title

Documentation Type

Missing documentation (feature not documented)

Documentation Location

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

Section/Topic

"Work from both surfaces at once" and "Connect from another device" session naming behavior for Remote Control sessions

Current Documentation

The Remote Control page currently says:

* Work from both surfaces at once: the conversation stays in sync across all connected devices, so you can send messages from your terminal, browser, and phone interchangeably 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.

The session naming workflow page also says:

Sessions created by claude -p or SDK invocations do not appear in the picker, but you can still resume one by passing its session ID or custom name to claude --resume <session-id-or-name>. Custom names set with --name or /rename are accepted in addition to session IDs.

What's Wrong or Missing?

Changelog v2.1.110 includes:

Fixed Remote Control session renames from claude.ai not persisting the title to the local CLI session

The docs explain CLI-side naming (--name, /rename) and how a Remote Control session gets its initial title, but they do not explain that renaming the session from claude.ai/code updates the same underlying local CLI session title.

That leaves an important cross-surface behavior undocumented: a user can rename a Remote Control session in the web UI, and that rename should persist back to the local CLI session rather than staying web-only. The docs also do not say whether the renamed title becomes the local resumable session name.

Suggested Improvement

Add a short note to the Remote Control page stating that session title changes made from claude.ai/code or the Claude mobile app persist back to the local CLI session because both surfaces are controlling the same session.

Suggested content outline:

• Under the Remote Control naming section, clarify that renames from the web/mobile UI update the local session title as well.
• State that the updated title is the session name Claude Code uses locally (prompt bar, resume flows, and other name-based session references).
• In the general session naming docs, add a cross-reference noting that Remote Control sessions can also be renamed from claude.ai/code, not only with --name and /rename.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/remote-control | Remote Control cross-device sync and session title behavior |
| https://code.claude.com/docs/en/common-workflows | Session naming and claude --resume <name> behavior |
| https://code.claude.com/docs/en/commands | /rename command reference |
| https://code.claude.com/docs/en/cli-reference | --name, --remote-control, and resume-by-name flags |

Total scope: 4 pages affected

Source: Changelog v2.1.110

Exact changelog entry: Fixed Remote Control session renames from claude.ai not persisting the title to the local CLI session