Desktop: Remote Control session from another machine renames local project's sidebar entry to show full path

Description

When a Remote Control session for a project is started on a different machine (Machine B) than the one running Claude Desktop (Machine A), and that project has the same folder/repo base name as an existing local project on Machine A, the Desktop sidebar on Machine A renames the local project entry to include its full absolute path — even though nothing about the local project itself changed.

Before the Remote Control session on Machine B existed, the local project entry on Machine A displayed cleanly as the folder name only (e.g. web-pm-specifications). After a Remote Control session was used for a project with the same base folder name on Machine B, the Machine A sidebar started showing two separate entries grouped under that name:

• One labeled with a short fragment related to the other machine's path/context (in our case, a parent-folder-like label)
• One labeled with the local project's full absolute path (e.g. web-pm-specifications · C:\Users\<user>\claude-projects\buzzwoo\projects\web-pm-specifications)

Steps to reproduce

1. On Machine A, work locally in a project folder named e.g. my-project. Sidebar shows it simply as my-project.
2. On Machine B, start a Remote Control session (claude remote-control or --remote-control) inside a differently-located folder that also happens to be named my-project (or the same repo checked out at a different path).
3. Open Claude Desktop on Machine A and look at the Code tab sidebar.

Expected behavior

The local project entry on Machine A keeps its original display name (just the folder name), since nothing about it changed. The Remote Control-originated project (which has no local cwd on Machine A at all) should be disambiguated on its own, without forcing a rename of the unrelated local entry.

Actual behavior

Both entries get a disambiguating suffix once they're grouped together by base name, including the previously-clean local entry, which now permanently shows its full local path instead of just the folder name — even after the Remote Control session on Machine B ends.

Additional context

We verified this isn't a project-path/encoding bug on the local side: every local session file for the project on Machine A (%APPDATA%\Claude\claude-code-sessions\<account>\<workspace>\local_*.json) has an identical, correct cwd. The session that appears under the other label has no corresponding local session file anywhere on Machine A, consistent with it running entirely on Machine B per the Remote Control docs ("Remote Control sessions run directly on your machine").

We searched existing issues for remote control project name duplicate sidebar and didn't find an existing report matching this specific symptom.

Environment

• OS: Windows 11
• Claude Desktop, Code tab
• Remote Control feature (research preview)
• Desktop app version: not confirmed by reporter at time of filing — happy to add on request