Remote control of a Claude Code session requires being physically at the host machine to enable

Problem:
Remote control of a Claude Code session (via the iPhone app / claude.ai) currently needs a slash command run locally, on the host machine itself, for each session before it can be remote-controlled. If you didn't run that command on a given session before leaving the machine, there's no way to enable it remotely later — you have to be physically there.

Why this is a real problem:
In practice I run several parallel Claude Code sessions across different projects on my desktop. When I travel, I only think to enable remote control on the one or two sessions I expect to need. Inevitably, a need comes up for a different session I didn't bootstrap in advance — and at that point I'm stuck for however long I'm away, with no way to reach it except asking my active session to relay messages to it (which, correctly, that session refused to act on without hearing from me directly — so the relay doesn't actually work as a substitute).

Suggested improvement:
Some way to enable remote control on a session I didn't pre-authorize locally — e.g., from the phone app, being able to see the list of running sessions on a paired machine and request/enable remote control on one of them remotely, rather than needing the initial slash command to originate on the machine itself.