▶ YouTube Summaries

• YT :: https://www.youtube.com/watch?v=UvcH1hKM-mQ
• Original title :: How I work from anywhere with a multi-machine setup

Kun Chen describes how three devices - a 14-inch M5 MacBook Pro (24 GB), a headless M4 Mac Mini (64 GB) and an iPhone - form one fleet for agentic engineering. The laptop stays the primary interactive machine, the Mac Mini runs always-on remote workers, Tailscale links everything into one private network, Herdr gives a single terminal view across machines, Firstmate orchestrates agents (with remote Secondmates on the Mini), and the phone connects over SSH through his own app SSHHIP. The Mac Mini setup is delegated to an agent via a headless skill, with a manual walkthrough for those who prefer it.

Machines and roles

• MacBook Pro (M5, 14-inch, 24 GB) :: primary workstation, used interactively; runs Firstmate (the main orchestrator agent); also used for gaming (WoW launch day shown in passing).
• Mac Mini (M4, 64 GB) :: headless, on a bookshelf (poor ventilation; a new open shelf is on the way); runs remote workers.
• iPhone :: carried everywhere, used to reach the other machines.
• Spare machines :: left for a future video.

Why the laptop is primary

• Alternative considered :: Mac Mini as primary, laptop as thin client. Benefit: always on, nothing stops when the lid closes.
• Decisive advantage of the laptop :: nothing stands between the user and the work. Everything travels along (coffee shop, meeting, flight) and works under bad network conditions.
• Latency problem with SSH to the Mini :: even around 100 ms between keystroke and terminal update breaks the flow of Neovim keyboard motions.
• Lid-closed mitigation :: a single command lets the laptop keep running (agents keep working) with the lid closed, so it can be carried around without being held half open.

Headless Mac Mini: manual steps on the machine

Only a few steps need a physical monitor, mouse and keyboard; the rest is done remotely.

• Create a separate administrator user :: kept apart from the personal account because the account is later handed to the agent; gives isolation so personal things are not messed up.
• Turn on Remote Login (SSH) :: in settings, switch it on and allow the new user.
• Same network :: the Mini and the controlling machine must be on the same Wi-Fi or the same router/switch for the initial setup.
• Note the local hostname :: it is the name used later to connect.

Delegating the rest to an agent

• From the laptop, launch any agent (Claude, Codex, Pi, ...) and give it the Mini hostname, asking to set the machine up as always-on headless.
• The author uses a skill called headless (a public repo) that encodes common practices; the agent is told to use that repo for the setup.
• Reason for delegating :: doing it manually puts the maintenance burden on the user; if the agent does it from day one, the agent holds all context and can keep managing the machine without involvement.

Manual headless configuration

• FileVault off :: with it on, every power loss or restart requires a physical password entry. Useful on a laptop, pointless on a headless machine at home.
• Automatic login :: enabled for the new agent account (not the personal one), so the machine stays logged in after restarts.
• Energy settings :: prevent automatic sleeping, disable hard disk sleep, enable wake for network access, always start up when power is connected. Together they make the machine return after power loss or restart.

Tailscale

• Not affiliated; the free tier has been enough for personal use.
• Problem solved :: same-network requirement. Away from home Wi-Fi, the laptop cannot reach the Mini directly.
• Tailscale builds a private virtual network; every device (phones, Macs, PCs, Linux boxes) gets an IP address and a name, and all reach each other regardless of location (home Wi-Fi, another house, mobile network).
• Once the Mini is in the tailnet it is ready to run work.

Herdr

• Described as a modern tmux: many sessions, panes and tabs in a terminal.
• Remote machines can be added to the same view: give the machine name (Mac Home), a label (Mini) and the session to attach to (FM Remote). All sessions on the remote machine then appear, and new ones can be created and commands run there.
• Result :: all machines managed from one Herdr view.

Firstmate and remote Secondmates

• Firstmate :: talk to one agent that orchestrates a large team of agents. Setup: clone the repo and launch the agent harness (Claude) in that directory.
• By default Firstmate runs agents only on its own machine.
• Remote Secondmate :: another Firstmate running on a different machine. The local Firstmate assigns work to it, and it orchestrates work there.
• Example prompt :: set up a remote second mate on Mac Home for the GitHub project runner-up. Firstmate does the rest of the setup; afterwards all work on that project happens on the Mini, with many Secondmates running there.
• Offline resilience :: most orchestration is done by the remote Secondmates, so when the laptop is offline or asleep the Secondmates and their crew mates keep working; on return, Firstmate catches up on what happened.

Working from the phone

• Install the Tailscale app on the phone so it joins the tailnet; then any machine is reachable by Tailscale IP or name from anywhere.
• An SSH client is needed; the author uses his own app SSHHIP (iOS now, Android coming soon), though other popular apps work too.
• Connecting to the laptop shows the very same Herdr session used at the desk. Reason for staying in the terminal: everything is available with a consistent experience from anywhere.
• Main pain point is the mobile keyboard, which motivated building the app: SSH from a phone should almost never need the keyboard, ideally operable with one hand.
• Dial interface :: a control at the bottom of the screen; hold and drag towards an action, and the dial expands with more option groups covering common needs. Frequent commands can be saved (examples: ahoy, lavish).
• Voice input :: transcribed on device, no subscription needed. Demo: dictating "explain this decision to me" to Firstmate, which returned a report with a link to an interactive visual artifact readable on the phone, like on the laptop.

Closing

More topics around the multi-machine setup are promised for future videos; viewers are invited to comment on what they want to see.