[DOCS] Remote Control docs omit web UI title persistence and precedence

Documentation Type

Missing documentation (feature not documented)

Documentation Location

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

Section/Topic

"Connect from another device" and the Remote Control session title selection rules

Current Documentation

The Remote Control page currently says:

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 claude.ai/code session-management page currently says:

Sessions appear in the sidebar at claude.ai/code. From there you can review changes, share with teammates, archive finished work, or delete sessions permanently.

No code.claude.com page I found explains that Remote Control session titles can be changed from the web UI, or that a title set there should be treated as a custom title rather than being replaced by later auto-generated title updates.

What's Wrong or Missing?

Changelog v2.1.108 includes this entry:

Fixed Remote Control session titles set in the web UI being overwritten by auto-generated titles after the third message

That fix confirms two user-facing behaviors that are not documented clearly today:

A. Remote Control titles can be set from the web UI

The current Remote Control docs only list explicit titles coming from CLI arguments or /rename. They do not say that a title changed in the claude.ai/code UI is also a supported custom-title path for Remote Control sessions.

B. Web-set titles should win over later auto-generated title refreshes

The docs explain auto-generated naming, but they do not explain that once a user sets a title manually in the web UI, Claude should preserve that title instead of replacing it with the auto-generated title refresh that happens after additional conversation.

Without that guidance, Remote Control users cannot tell whether a title changed in claude.ai/code is meant to be durable or just a temporary UI label.

Suggested Improvement

Update the Remote Control docs to describe web UI renaming as another explicit title source and clarify its precedence over automatic title generation.

Suggested minimum fix:

1. In remote-control, expand the title-order section to include titles set from claude.ai/code (and the mobile app, if they behave the same way).
2. State that manually set titles from the web UI are treated like other custom titles and should not be overwritten by later auto-generated title refreshes.
3. In the claude.ai/code session-management docs, add rename alongside archive/delete anywhere the session title menu is described, with a short cross-reference back to Remote Control session naming behavior.

Example wording for the Remote Control page:

If you rename the session from claude.ai/code or the Claude app, that title becomes the session's custom title and future automatic title updates do not overwrite it.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/remote-control | Documents Remote Control title selection, but only lists CLI and /rename as explicit title sources |
| https://code.claude.com/docs/en/claude-code-on-the-web | Session management for claude.ai/code mentions archive/delete but not rename in the general overview |
| https://code.claude.com/docs/en/routines | Mentions renaming a web session from the title dropdown, which suggests the capability exists but is not tied back to Remote Control title precedence |

Total scope: 3 pages affected

Source: Changelog v2.1.108

Exact changelog entry: Fixed Remote Control session titles set in the web UI being overwritten by auto-generated titles after the third message