Setting Up a Spare Mac for Claude Code: The Full Remote Control Guide

A new guide making the rounds on Hacker News explains how to set up a dedicated Mac as an isolated environment that Claude Code can fully control. The setup enables remote access via SSH, the Claude mobile app (Remote Control), or Screen Sharing - essentially creating a sandboxed machine where an AI agent can operate with minimal risk to your primary workstation.

The guide by ykdojo covers 16 steps from fresh setup to Tailscale remote access. Let's break down what it involves and what the HN community thinks about this approach.

The Core Setup#

The guide targets developers who want Claude Code running on a separate machine they can interact with from anywhere - their main Mac, their phone, or over the network. The key principles:

Isolation first. Create a fresh macOS account with no Apple ID, no personal data, and no cloud sync. If Claude does something unexpected, the blast radius is contained to a throwaway environment.

SSH as the backbone. The target Mac runs SSH with key-based authentication. Your primary machine can connect without passwords, enabling scripts and Claude itself to execute commands remotely.

Passwordless sudo. For Claude to install packages, modify system settings, or run privileged commands, the account gets NOPASSWD sudo access. This is a security tradeoff - documented in the guide - that enables autonomous operation.

Multiple access paths. The setup supports:

• Direct SSH from your terminal
• Claude Mobile app's Remote Control feature (tmux-based)
• macOS Screen Sharing for GUI access
• Optional Tailscale for access from anywhere

What HN Is Saying#

The Hacker News discussion has 106 comments and reveals polarized views on AI agent automation.

"What are they doing running agents 24/7?" This was the most upvoted skeptical comment. One user asked: "I still don't understand what these freaks are doing running these agents 24/7 on machines. What are they doing? Managing a todo list?"

Defenders pointed to concrete workflows:

• Scanning logs for errors, auto-triaging issues, opening PRs
• Running fuzzing campaigns with domain-specific knowledge
• Progressing side projects during commute time
• On-call triage - having Claude investigate alerts and summarize findings

Dispatch vs. direct setup. Several commenters already use Claude Desktop + Dispatch on a Mac Mini. The guide's approach differs in that it uses Claude Code (CLI-based) rather than Claude Desktop, and enables more flexibility in container permissions. One noted: "Dispatch/Cowork won't download and fill out or read PDFs or other files due to container permissions. Vanilla Claude Code has no problem using curl and wget."

The satire detector is broken. One commenter jokingly described using Claude to automate Tinder swiping - scheduling dates automatically and providing chat history summaries. Someone replied "I totally believed this. We live in a dystopia already." Another linked to a real GitHub project attempting exactly that.

Power users vs. skeptics. The thread crystallizes a divide. Power users describe setups where they kick off agent tasks in the morning and review results later. Skeptics question whether the overhead of verification - checking if the agent did a good job - is worth avoiding human involvement in the first place.

The Technical Details#

For those considering this setup, here are the key technical components:

Step 1-4: Base configuration

• Fresh macOS install with isolated local account (no Apple ID)
• Enable Remote Login (SSH) in System Preferences
• Configure passwordless sudo via visudo
• Get the hostname or IP for network access

Step 5-7: Remote access

• Generate SSH keys and copy to the target Mac
• Prevent sleep mode with caffeinate or Energy Saver settings
• Optional: encrypted clipboard sync between machines

Step 8-11: Claude Code

• Install Claude Code via the standard installation script
• Configure environment (Node.js, Python, dev tools)
• Authenticate with Claude and GitHub
• Enable computer use capabilities via tmux workaround

Step 12-16: Extended access

• VPN and additional applications
• Remote Control from Claude mobile app
• Chrome extension for browser automation
• Screen Sharing for GUI access
• Tailscale for peer-to-peer networking from anywhere

The tmux piece is notable: Claude Code's computer use features (screenshots, input control) work through a tmux session that persists across connections. This enables the Claude mobile app to connect to ongoing sessions.

When This Makes Sense#

The honest assessment: this setup is overkill for most developers. But there are legitimate use cases:

Parallel agent workloads. If you're running multiple Claude Code sessions - one exploring a codebase, another writing tests, another handling documentation - having them on a separate machine keeps your primary workstation responsive.

Mobile-first development. Some Claude Code power users have stopped using traditional IDEs entirely. They kick off tasks from their phone while commuting and review results later. A dedicated Mac enables this workflow without exposing personal data.

Burning subscription tokens. Claude Max subscribers have usage caps that reset periodically. Running agents on background tasks ensures you're getting value from the subscription even when not actively coding.

Home automation and personal projects. Several commenters described using this for projects they don't have time to sit at a keyboard for - home automation scripts, content pipelines, personal tools.

The Security Considerations#

The guide explicitly acknowledges the tradeoffs:

• NOPASSWD sudo means any compromise of the Claude Code session gives root access
• No Apple ID means no iCloud, no Find My Mac, limited recovery options
• Network exposure via SSH requires proper key management
• Agent autonomy means trusting Claude's judgment on what to execute

The isolation model - fresh account, no personal data, dedicated hardware - is the mitigation. If something goes wrong, you wipe the machine and start over.

Should You Do This?#

For tinkerers and AI enthusiasts - sure, it's a fun setup to explore. The guide is well-documented and the 16 steps are manageable for anyone comfortable with SSH and macOS system preferences.

For production use, the calculus depends on your trust in agent autonomy. The HN thread's most honest take: "If you can't think up enough coding projects to keep an agent busy in the background that's a skill issue on your side."

Whether that's wisdom or cope is left as an exercise for the reader.

Sources#

• Setting up your spare Mac for Claude Code to control
• HN Discussion
• Claude Code Documentation