[BUG] Claude Desktop archived an active Remote Control session overnight without user action (history inaccessible, no undo) #67811

Preflight Checklist

• I have searched existing issues and this hasn't been reported yet
• This is a single bug report (please file separate reports for different bugs)
• I am using the latest version of Claude Code

What's Wrong?

A long-running Remote Control session (started with /remote-control from Claude Code CLI on a Linux host, attached in the Claude Desktop app) was archived overnight with no user action. In the morning the session no longer appeared in the Desktop session list and its history was not accessible from Desktop. No archive command, shortcut, or prompt was triggered by the user — the machine was idle overnight.

This is the second history-loss event for the same workflow within a week:

1. Earlier, an accidental Ctrl+T press in Claude Desktop archived the remote-control session and its visible history instantly, with no confirmation and no way to undo (related feature request: [FEATURE] Unarchive Claude Code sessions in desktop app option #30869 — no unarchive in Desktop).
2. This time the archive happened autonomously overnight, with no keypress at all.

The underlying CLI session was unaffected (the terminal session continued to work and history is intact in ~/.claude/projects/.../*.jsonl), so this appears to be Desktop-side archive state being applied to a live remote-control session — possibly an idle/auto-archive policy. Related: #39178 reported server-side auto-archive during idle periods (closed as stale), and #65838 shows archive state is tracked per-client.

Expected Behavior

• A remote-control session that is still alive on the CLI side should never be auto-archived by a client app, regardless of idle time.
• Archiving should require explicit user intent (and ideally a confirmation for sessions with an active backing process), and should be reversible from the Desktop UI.

Steps to Reproduce

1. On a Linux host, run claude and start /remote-control.
2. Attach to the session from the Claude Desktop app.
3. Leave both ends idle overnight (~8+ hours).
4. Open Claude Desktop in the morning: the session is archived / missing from the session list; history is not viewable from Desktop. The CLI session is still running.

(Not yet confirmed deterministic — happened once overnight; the earlier Ctrl+T loss was a separate, user-triggered path.)

Environment

• Claude Code CLI: 2.1.175, Linux 5.15.0-173 x86_64 (remote-control host)
• Client: Claude Desktop app (session list / archive behavior is on the Desktop side)