Feature request: Claude Desktop SSH remote — session should survive client disconnect (reconnect/resume)

When Claude Desktop's SSH remote client disconnects — intentional quit, network drop, laptop lid close — the Claude Code process on the remote server terminates with it. There's no way to reconnect and pick up where you left off.

Verified this today by starting a long-running background bash script (logging a tick every 30s to a file) via the SSH remote session, then disconnecting the client. On reconnect: the bash process was still running and logging fine, but the Claude Code session itself was gone — no way to resume the conversation or see the in-flight tool calls.

For comparison, Codex CLI keeps the session alive server-side; reconnecting reattaches to it, essentially tmux-style. The current workaround for Claude Code is to manually wrap claude inside tmux before connecting, which sidesteps the integrated SSH remote feature entirely.

Expected behavior: the server-side Claude Code session stays alive on client disconnect, and Claude Desktop reattaches to the existing session on reconnect. A --detach/--attach CLI pair would also cover headless cases.

Environment:

• Local client: Claude for Mac 1.3109.0 (35cbf6)
• Remote: Claude Code 2.1.112 on Linux

Related: #49644 (Terminal panel disabled in remote sessions)