Archiving a Remote Control session also archives and kills a different, live session with the same name

What happened

Archiving an old, finished Remote Control session on claude.ai also archived — and terminated — a different, currently live session that happened to share the same Remote Control name. Three live sessions died in a single archiving pass.

Unarchiving restores the web record, but the local claude process is already gone, so the session comes back blank/unusable.

Setup

Sessions run on an always-on Mac Mini, started as:

tmux new-session -d -s cc-<project> "claude --remote-control cc-<project>"

The launcher reused one Remote Control name per project (cc-thyself, cc-birds_nyc, …), so over weeks many distinct sessions shared a single name. Sessions are steered from the iOS app / claude.ai.

Steps to reproduce

1. Start a Remote Control session named foo. Use it, then stop it.
2. Later, start a new Remote Control session, also named foo. Leave it running.
3. On claude.ai, archive the old finished foo session.
4. The live foo session is also archived, and its local claude process exits — the tmux session dies with it.

Expected

Archiving affects only the selected session, and never terminates a session that is currently live.

Actual

Archiving one session archived and killed same-named sessions, including a live one mid-task. Unarchive does not (and cannot) bring the terminated process back.

Notes

• Reproduced 2026-08-04 across three separate projects in one archiving pass.
• Also observed: immediately re-creating a Remote Control session with a name that was just used caused it to exit within ~20s, while using a fresh unique name worked fine — consistent with sessions being keyed by name rather than by id.
• Workaround: give every launch a unique --remote-control name (e.g. a timestamp suffix).

Environment

• macOS 15 (Darwin 24.6.0), Apple silicon
• Claude Code CLI 2.1.221, Remote Control sessions inside tmux