The guide from ykdojo.github.io shows how to turn a spare Mac into an always-on machine that Claude Code can fully control, letting you talk to it from your phone via the Claude app or from your main Mac over SSH. The author recommends a separate spare Mac because Claude Code, especially when run with the --dangerously-skip-permissions flag, carries inherent risk on a main machine and a dedicated device eliminates or mitigates those risks. The guide favors running the agent on a full Mac rather than a container for cases that require Mac-only apps like Unity or direct computer-use actions such as clicking and dragging, noting containers still route network requests through the main machine and have capability limits. Practical steps include erasing the target Mac if it holds sensitive data, optionally updating macOS, granting the terminal Full Disk Access so sudo can run without repeating password prompts, creating a sudoers rule for passwordless sudo, and testing with sudo -n true. The author recommends reaching the target machine by hostname rather than IP because hostnames remain stable while IPs can change. The stated tradeoff is that giving the agent full access makes the spare Mac useful and feature-complete but means it should be a machine "that has nothing to lose."
