[FEATURE] "My Devices": start a Remote Control session on a machine that has no session running

Problem

Remote Control currently has a chicken-and-egg constraint: to drive a machine from the phone or web app, that machine must already have a Claude Code session running with remote control enabled. If I am away from my desk and nothing is running there, the desktop is unreachable — even though the app is signed in on it.

Because of that, the practical workaround is out-of-band and worse in every dimension: people keep SSH credentials in a note and paste them into each new chat so the agent can reach the other box. Long-lived secrets end up in conversation transcripts and in model context, which is a strictly worse security posture than a first-class path would be.

Proposal

A "My Devices" surface in settings, listing machines where the app is (or recently was) signed in:

• device name, OS, last seen, online/offline
• a per-device opt-in toggle: "allow starting sessions remotely" — off by default
• from the mobile/web session picker, select a listed device and start a new session on it

The key difference from what exists today: the target device does not need a session already running.

On the safety objection

The obvious objection is blast radius — an agent that can enumerate and reach a fleet turns one prompt injection into lateral movement.

But the product already ships --dangerously-skip-permissions, which hands an agent a full machine behind a single explicit opt-in. A per-device enrollment toggle is a narrower grant than that. And it replaces a status quo in which users paste long-lived SSH keys and passwords into chat messages, which is not a safer equilibrium — just a less visible one.

Scope note

The genuinely hard part here is reachability (NAT, sleeping laptops, roaming IPs), not the UI. A useful first cut can sidestep that entirely:

• manual enrollment only — no auto-discovery
• only devices that currently hold an authenticated app connection
• optionally, user-declared SSH aliases as device entries

That alone would cover the common case of "my desktop is on, I am not at it".

Related issues

• #70546 — no way to programmatically start a Remote-Control-visible session from an already-running session
• #37589 / #46317 — auto-enable remote control at session start (partial workarounds for the same chicken-and-egg)
• #82403 — start a new session in the host session's local directory from mobile

All of the above assume a session or host process already exists. This request covers the case where nothing is running on the target device at all.