[BUG] Remote Control registration ignores persisted /rename title after /resume

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

When resuming a previously renamed session, the local CLI correctly restores the renamed title (shown in the bottom-right corner), but the Remote Control registration on claude.ai/code and the Claude mobile app shows the auto-generated <prefix>-<random> name instead.
Per the docs (https://code.claude.com/docs/en/remote-control), the session title resolution order is:

--name / --remote-control "..." argument
Title set with /rename
Last meaningful message in conversation history
Auto-generated <prefix>-<random>

Item 2 should apply on resume, since the renamed title is persisted (CLI reads it back correctly). It appears the Remote Control registration on resume falls through to item 4 instead of consulting the persisted /rename title.

What Should Happen?

Remote Control registration on resume picks up the persisted /rename title (resolution order #2) before falling back to the auto-generated name (#4).

Error Messages/Logs

Steps to Reproduce

• Have "Enable Remote Control for all sessions" set to true in /config.
• Start a fresh claude session in a project directory.
• Run /rename my-session-name.
• Confirm the renamed title appears in the Claude Android app / claude.ai/code session list. ✅
• Exit Claude Code.
• Start claude again, run /resume, select the same session.
• CLI bottom-right shows my-session-name (correct). ✅
• Claude Android app / claude.ai/code session list shows <hostname>-<random-word> instead of my-session-name. ❌

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.143

Platform

Anthropic API

Operating System

Other Linux

Terminal/Shell

Other

Additional Information

_No response_