Repository navigation
Archiving a Remote Control session also archives and kills a different, live session with the same name #83917
Description
Activity
Closing this — I misdiagnosed it, and the cause turned out to be local.
The real cause was a cron job of mine (an hourly scheduler for one project) whose tmux lookup matched
cc-*instead ofcc-<that-project>. On the branch where it clears finished sessions, it killed every Remote Control session on the machine, including live ones belonging to unrelated projects. Its log shows exactly that at 12:07 and 13:07, matching the moment the sessions died.Because the underlying process was killed, those sessions then showed up as archived/dead on claude.ai, and "unarchive" could not bring them back — which is what led me to blame archiving. Archiving was a symptom, not the trigger.
Leaving one observation in case it is useful: immediately re-creating a Remote Control session reusing a name that had just been used exited within ~20s, while the same command with a fresh unique name worked. That may be nothing, and I have not reproduced it deliberately. If it is worth its own report I will file a clean one with a proper repro rather than leave this inaccurate issue open.
Apologies for the noise.
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.
- locked as resolved and limited conversation to collaborators
on Sep 25, 2026
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
claudeprocess is already gone, so the session comes back blank/unusable.Setup
Sessions run on an always-on Mac Mini, started as:
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
foo. Use it, then stop it.foo. Leave it running.foosession.foosession is also archived, and its localclaudeprocess 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
--remote-controlname (e.g. a timestamp suffix).Environment