The Mac Mini stays home
A month ago I wrote that the bottleneck moved again: a dozen agents, a dozen worktrees, test databases and dev servers, all on one laptop. By the afternoon the machine, not me, was deciding how fast work moved.
So I got a Mac Mini with 64 GB of RAM. It fixed the problem on day one. It also created a new one: I go into the office two days a week, and carrying a Mac Mini to the office feels ridiculous.
My company let me keep the old laptop. So the plan is simple. The Mini stays home and does the work. The laptop comes with me and becomes a window into the Mini.
I asked Claude to check the idea
A while back an AI suggested this setup and said Tailscale would make it free. Before setting anything up, I asked Claude Code, running on the Mini, to research whether that was true and how people actually work this way.
The answer was yes, with two catches I hadn't heard about:
- Tailscale's free plan is for non-commercial use. It's generous (up to 6 users, unlimited devices), but the pricing page says it's "only suitable for non-commercial use." Two work machines doing work is work. That means either a paid plan or a clear OK from the company, and I'd rather know that now than find out later.
- Disk encryption and remote restarts don't mix. Every "Mac Mini home server" guide says to turn off FileVault so the machine can restart on its own. My company expects disk encryption, so that's out. And with FileVault on, a Mac that restarts sits at the unlock screen. Tailscale isn't running yet, so from the office it's simply gone.
The second one changed the whole plan. The goal isn't "it can restart on its own". It's "it never restarts while I'm away".
Get the next note like this by email.
about one a week · no spam · one-click out · or rss
What Claude found on the Mini
Then Claude looked at how the Mini was actually set up. Four things would have broken this:
- It went to sleep after one minute. It only stayed awake because apps happened to be keeping it up.
- Restart after a power failure was off.
- macOS updates installed automatically. That's an unattended restart straight into the unlock screen, on a day I'm at the office.
- It was on Wi-Fi, not Ethernet.
None of these were obvious to me. I'd have found the update one the hard way, from the office, with nothing to connect to.
Setting it up
Claude did what it could and handed me the rest. Installing Tailscale and changing power settings need my admin password, which an agent can't type, so it gave me three commands to paste into a regular Terminal:
$ brew install --cask tailscale-app $ sudo pmset -a sleep 0 disksleep 0 womp 1 autorestart 1 $ sudo defaults write /Library/Preferences/com.apple.SoftwareUpdate AutomaticallyInstallMacOSUpdates -bool false
The Mini never sleeps now (the screen still does), it restarts after a power cut, and updates download but wait for me. I install them on days I'm home. I turned on Remote Login and Screen Sharing in System Settings and signed in to Tailscale.
Then Claude checked its own work: SSH and Screen Sharing both answered on the Mini's Tailscale address, not just locally. Ethernet will have to wait for another day.
The laptop's half
The last step happens on the laptop, so I asked for a prompt I could paste into Claude Code there. It sets up an SSH key and a mini shortcut, checks that the laptop can see the Mini, and explains the daily routine:
ssh mini, then everything runs inside tmux, so a closed lid or a dropped Wi-Fi connection doesn't kill anything.- VS Code's Remote-SSH opens the Mini's files on the laptop. Builds, tests, Postgres and Docker all run on the Mini's RAM.
localhost:3000on the laptop is the Mini's dev server. - Screen Sharing when I need the Mini's whole desktop.
The part that needs no VPN at all
The best surprise was in Claude Code itself. Remote Control (claude remote-control on the Mini) lets me drive a session running on the Mini from claude.ai or the Claude app on my laptop or phone. The Mini only makes outbound connections, so there's no VPN and no open ports.
For most of what I do, that's enough. Tailscale is for everything else: the editor, the dev server, the full desktop.
What this changes
For years, "my computer" meant the thing in my bag. Now it's a box on a shelf at home, and the laptop is just the screen I happen to be holding. The machine doing the work doesn't move, so it doesn't need a battery, a lid or a bag. It needs RAM, power and a network connection.
The whole setup took one conversation. Claude researched it, found the catches, checked my actual machine, told me which commands only I could run, and then checked that they worked. My part was typing a password and flipping two switches.
Liked this? Get the next note by email.
about one a week · no spam · one-click out · or rss