[Feature Request] Support attaching to running Claude Code sessions from Desktop app instead of spawning duplicate processes

Bug Description

I run about 20 long-lived Claude Code sessions on one Windows 11 machine, started in Windows Terminal with claude --resume <id> --name <name>, and I use the Claude Desktop app as a remote for them. The terminal is the home because terminal sessions have cross-session messaging and the full tool set, which the desktop Code tab does not (held inbound messages expire there). Three questions:

When the desktop Code tab opens a session that is already running in a terminal, it starts a second process on the same transcript; the two drift apart within hours, and the docs only say to close the terminal first. Is Remote Control the intended way to use the desktop as a remote for a terminal session, and is attaching to a running process through the Code tab planned?

Session names: a rename in the terminal (--name, /rename) is sometimes overwritten on reconnect by the title stored on claude.ai, and an archived claude.ai session reappears after the local session reconnects. Which title is meant to win, and is there a way to retire a claude.ai session record for a session that is still live locally under a new name?

After a reboot, claude --resume on a large transcript offers "resume from summary"; the resumed session then cannot recall earlier turns verbatim. What is the recommended way to keep a resumable, accurate record for sessions that run for weeks?

Open to other modes of operation or being directed to a best practice. I am not trying to devise a new method.

Environment Info

• Platform: win32
• Terminal: windows-terminal
• Version: 2.1.291
• Feedback ID: 3f03a18c-38e4-4c86-9878-893b689b3ff1