Remote Control drops session name passed to /remote-control (desktop/GUI) — silently falls back to hostname auto-name

What happened

Naming a Remote Control session by passing a name to /remote-control (from the desktop GUI app) does not take. The session shows up in claude.ai/code / the mobile app's session list with the default auto-name — <hostname>-<random-suffix> (e.g. wmpcmacbookpro1-local-misty-star) — instead of the name I provided. The passed name is dropped with no error or warning.

Because the fallback is silent, from another device I get a list of similarly-named <hostname>-<random> sessions with no indication of which project/repo each is tied to.

Steps to reproduce

1. In a running desktop-app (GUI) session, run /remote-control "my-name" (or /rc "my-name").
2. From another device, open claude.ai/code (or the Code tab in the mobile app) and look at the Recents list.

Expected

The remote session appears named my-name.

Actual

It appears as <hostname>-<random> (e.g. wmpcmacbookpro1-local-misty-star); the name argument is ignored, with no feedback that it was dropped.

Notes / narrowing

• /rename <name> after enabling Remote Control works and propagates to the list — so only the name argument to /remote-control is affected, not naming in general.
• Suspected cause: the name argument to /remote-control is honored on the terminal CLI but not from the desktop GUI (similar to the VS Code extension not accepting the name arg), and it fails silently rather than surfacing that the arg was ignored.
• Minor secondary ask: showing the session's working directory / repo in the remote session list would make multiple same-host sessions distinguishable even when auto-named.

Environment

• Claude Code 2.1.201
• macOS
• Session started/enabled from the desktop GUI app (not terminal CLI, not VS Code)
• Auth: claude.ai OAuth (Max plan)