Stale/duplicate session titles + no wrong-session safeguard → silent data loss in Bypass-permissions mode

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?

Claude Code session titles are auto-generated from the first message and never update as the work pivots, so long-lived sessions become misnamed. When several sessions on one project start with similar first messages, they are near-indistinguishable in the mobile session list and on desktop. This makes it easy to send an instruction to the WRONG session.

If that target session is in Bypass-permissions mode, the misrouted command executes with NO confirmation prompt — silent commits/deletes/overwrites in the wrong repo or branch, with no undo. The typo isn't the real hazard; wrong-session + bypass-permissions is.

Real example (today): three concurrently-live sessions — "Build 3D combo lab with animation", "3D Combo Lab authoring surface", and "Encode Combo Lab 3D decisions" — where the one titled "Build 3D combo lab with animation" had actually become the MCP/infra session. The title no longer matched its contents at all, and a sibling session was running in Bypass-permissions mode.

Surfaces involved: desktop app + mobile app with Remote Control.

What Should Happen?

Session titles should track what a session is actually about — auto-retitle (or prompt to retitle) when the topic drifts from the first message, with an easy manual rename on BOTH desktop and mobile.

Near-identical titles should be disambiguated in the list (append branch / cwd / a short session id).

There should be a strong, persistent indicator of which session is currently focused, plus a confirm-on-target when switching sessions via Remote Control.

Safety backstop: the FIRST mutating command after a Remote-Control session switch should require explicit confirmation even in Bypass-permissions mode, so a misrouted instruction can't silently modify the wrong repo/branch.

Error Messages/Logs

Steps to Reproduce

1. Start several Claude Code sessions on the same project, each with a similar opening message (e.g. multiple "3D combo lab" chats).
2. Let their actual work diverge over time — one becomes infra/MCP setup, another stays the original task.
3. Open the session list on mobile AND on desktop: titles are still frozen at each session's first message, and several read almost identically.
4. Switch between sessions via Remote Control. There is no strong, persistent indicator of which session is currently focused, and the near-identical titles don't disambiguate.
5. Type an instruction intended for one session — it is easy to send it to the wrong one. If the target session is in Bypass-permissions mode, it executes immediately with no confirmation.

Claude Model

None

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

N/A — used via the Claude Code desktop app + mobile app with Remote Control; no standalone CLI is installed on this machine, so claude --version is unavailable. Auto-update channel: latest.

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

_No response_