Comment by KronisLV
13 hours ago
> Unlike Claude Code on the web, which runs on cloud infrastructure, Remote Control sessions run directly on your machine and interact with your local filesystem. The web and mobile interfaces are just a window into that local session.
For the vibe'y workflows, this would easily solve parallel long running work without skipping permissions: schedule 10 different tasks and go for a run. Occasionally review what the hallucination machine wants to do, smash yes a few times, occasionally tell it not to be silly, have a nice run. Essentially, solving remote development, though perhaps not quite in the way how people usually think of it.
> Limitations
> One remote session at a time: each Claude Code session supports one remote connection.
Hmm. Give it 1-12 months.
This comment sounds like the basis for a nice Black Mirror episode.
Ehh, I think it's hardly different from the people who leave Claude Code working on problems overnight with really loose permissions - seemingly the chance of them returning to it mining crypto for Putin is low enough for it to not be a consideration (see the whole OpenClaw movement).
And people have been remoting into their machines for a while, so now having a pretty-UI-but-walled-garden variety doesn't ring that many alarm bells. If they manage to get it right, it wouldn't be that much different from running some CI stuff on your machine while you're making tea, or reviewing pull requests while lounging around.