Remote Control: allow --continue / --session-id to keep multi-session mode (or restore all sessions of an environment)

Problem
claude remote-control (multi-session, same-dir spawn) works well until the server process ends. After a reboot, or after a long sleep (several hours) on Windows, all of that environment's chats drop out of the Claude app sidebar. The only ways back are:

• Start a fresh server. This creates a new environment and a new sidebar section, and the previous chats are no longer grouped under it.
• Reattach with --continue / --session-id. This brings one previous chat back, but the server then runs in "Single session · exits when complete" mode, so no new chats can be opened in that folder.

So you can either keep your chats or have multiple chats, not both.

Environment

• Claude Code 2.1.286, Windows 11
• Servers started at login by a scheduled task: claude remote-control --chrome

Steps to reproduce

1. Run claude remote-control in a folder and open 2–3 chats from the app.
2. Reboot (or sleep the PC overnight).
3. Run claude remote-control --continue in the same folder → the server shows "Single session · exits when complete", and new chats can't be created.
4. Alternatively, run plain claude remote-control → there is a new environment, and the old chats are not shown with it.

Also observed

• --continue only accepts a bridge-pointer.json modified within ~4 hours and deletes older ones. So after an overnight sleep it fails even though the session still exists.
• Deleting a folder's last chat in the app terminates that folder's server.

Requested behaviour (any one of these would solve it)

1. A flag to resume an environment in multi-session mode, e.g. claude remote-control --continue --spawn same-dir. It would reuse the same environment ID and list its previous chats.
2. Or: a fresh server in a folder automatically reuses the folder's previous environment, so earlier chats stay in the same sidebar section.
3. Or: let --continue reattach regardless of the pointer's age, as long as the session still exists server-side.

Why it matters
Keeping Remote Control sessions always available, so you can code from your phone, means running them as a background service. Any service eventually restarts, and right now every restart breaks continuity.