Guide: Turn a Spare Mac into a Claude Code Remote Rig
20 Jul 2026
A newly published guide (via ykdojo.github.io) walks developers through configuring a spare Mac so it can be remotely controlled by Claude Code, Anthropic's agentic coding tool. The core idea: instead of running Claude Code with elevated permissions on your primary machine, offload that risk to a secondary device you already own but rarely use.
What the guide covers
The setup targets a common scenario—someone with a main Mac and a spare Mac lying around—and shows how to enable "computer use" so Claude Code can operate the spare machine directly. Key steps include:
- Enabling SSH on the target (spare) Mac so the source machine can connect remotely.
- Adjusting sleep settings, since macOS defaults to sleeping after roughly 10 minutes of idle time, which would otherwise interrupt a remote session.
- Installing Claude via a specific installer version (2.1.201) referenced in the walkthrough.
Once configured, the guide notes that the spare Mac can be accessed anytime from a phone through the Claude app, and it can also run Mac-only applications—Unity for game development is cited as an example—that might not be practical to run directly on a main machine.
The risk being addressed
The motivating problem is straightforward: running Claude Code with the --dangerously-skip-permissions flag on your main machine carries inherent security risk, since the tool gains broad, unchecked access to your primary environment. Isolating that risk on a spare device is the guide's proposed workaround.
But the fix introduces its own tradeoffs. Enabling SSH on a Mac can expose it to unauthorized remote access if not locked down properly, and the guide doesn't detail specific safeguards—like key-based auth, firewall rules, or network restrictions—that would typically accompany this kind of setup. There's also no information on hardware requirements, minimum macOS versions, setup time, or how many people have actually adopted this approach in practice.
Why founders should care
For early-stage teams experimenting with agentic coding tools, this pattern is worth watching, though it remains an informal, community-sourced technique rather than a vetted best practice:
- It's plausible that isolating risky automation permissions on a dedicated spare device reduces exposure on primary development machines, without eliminating risk entirely—SSH misconfiguration remains a real concern.
- Remote, phone-based access to Claude Code could likely support more flexible, mobile-first workflows for founders who want to check on or nudge agentic coding tasks outside normal working hours.
- A spare-Mac setup may offer a low-cost way to experiment with agentic coding tools before committing to more permissive configurations on core systems—useful for cash-conscious early teams testing new dev tooling.
What's still unclear
The guide leaves several open questions: what security hardening is recommended once SSH is exposed, what hardware or OS baseline is required, and how reliable the setup proves over time. Founders considering this approach should treat it as an early, unofficial pattern rather than a production-ready security model, and layer on their own access controls before exposing any machine to remote connections.