The ideal multi-machine Claude Code?

I run Claude Code on a Windows laptop, a Mac, and a couple of headless Linux boxes. The frustrating part isn't Remote Control. It works well.

It's that setting it up isn't a one-time investment. I SSH in, cd to the project, start tmux so the work survives a disconnect, launch claude with --remote-control.

tmux handles disconnections. It doesn't handle the machine being interrupted. If the box loses network for more than about ten minutes, Remote Control gives up and exits. And a reboot takes everything with it. Then I'm back to SSH'ing in & setting everything up again.

Also, I can only reach what I set up in advance. If I want to start a new project or work in a directory I didn't prepare beforehand, I can't. I have to go back to the machine first.

So the feature I feel is meant to free me is the one thing that keeps sending me back to each machine.

I've seen some partial workarounds — people wiring claude remote-control into systemd or a scheduled task so it comes back on its own. But from what I can tell, they help but don't fully solve these problems.

Here's what I think the ideal product experience could be:

https://docs.google.com/document/d/1UlIUMIJBQFRWX16T_Ebgm_htospKoYO4nHGGIDKGURw/preview

Short version: Install a Claude service on each machine — and have it designed to stay running, updated, machine-wide, and reachable from any Claude surface. Let users start a new project, pick up an old one, or run sessions in parallel by directing Claude remotely from anywhere without going back to your machines.

What do you think? Has anyone found a multi-machine setup that works well? What would you change?