Spare Mac for Claude Code: The Remote Control Setup Guide

Last updated: October 8, 2026 - re-checked against the guide (still 16 steps) and the HN thread (251 points, 196 comments)

To let Claude Code control a spare Mac, wipe it, create a fresh local account with no Apple ID, enable SSH with key authentication and passwordless sudo, keep it awake, install Claude Code, and connect from your phone with Remote Control. The guide by ykdojo lays this out in 16 steps, from a fresh setup to Tailscale access from anywhere, and it went through Hacker News in July.

This post breaks down what the setup involves, what the HN community thought, and where the risks are. The isolation is the point: Claude Code, especially with --dangerously-skip-permissions, carries inherent risk on your main machine, and a separate Mac with nothing to lose contains it.

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
• Remote Control from the Claude mobile app (/remote-control or claude remote-control)
• macOS Screen Sharing for GUI access
• Optional Tailscale for access from anywhere

What HN Is Saying#

The Hacker News discussion reached 251 points and 196 comments as of September 28 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
• Keep the Mac awake with pmset (sleep, clamshell and display sleep off while plugged in)
• Optional: encrypted clipboard sync between machines

Step 8-11: Claude Code

• Install Claude Code on the target over SSH with the native installer
• Optional step 9: an opinionated environment script (shell aliases, settings.json tweaks, the GitHub CLI, opt-in Playwright MCP and yt-dlp)
• Authenticate with Claude and GitHub
• Enable computer use capabilities via tmux workaround

Step 12-16: Extended access

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

The tmux piece is a workaround for macOS permissions: screen capture and input control are tied to the GUI login session, so the guide keeps a tmux server alive inside that session through a LaunchAgent, and every claude session created there inherits access to the display. The guide's ic helper starts those sessions with --dangerously-skip-permissions, which is exactly why the isolation steps come first. Remote Control is a separate step. Per the Claude Code docs, it works on Pro, Max, Team, and Enterprise plans (not API keys), the session keeps running on your machine, and it is unavailable if you use Bedrock, Vertex, or Foundry, or point ANTHROPIC_BASE_URL at another host.

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.

FAQ#

Can Claude Code control a Mac remotely?#

Yes. Claude Code runs on the spare Mac and you drive it over SSH from another Mac, or from your phone through Remote Control in the Claude app. The guide's optional computer-use step lets a session see and control the Mac's desktop, which needs a tmux workaround because of macOS permissions.

Why use a spare Mac instead of a container?#

The guide argues a container still runs on your main machine, sends network requests through it, and cannot run Mac-only apps that computer use might need to control. A dedicated Mac with no personal data gives the agent a full machine with nothing sensitive to reach.

Is passwordless sudo safe for an AI agent?#

It is a tradeoff the guide documents: any compromise of the Claude Code session gives root access on that Mac. The mitigation is isolation, meaning a fresh account with no Apple ID, no personal data, and hardware you can wipe.

Does Remote Control work with an API key?#

No. Anthropic's docs say Remote Control is available on Pro, Max, Team, and Enterprise plans and does not support API keys. See the Claude Code permissions guide for scoping what an unattended session may run.

What is the difference between Dispatch and this setup?#

HN commenters who use Claude Desktop with Dispatch on a Mac Mini said it hits container permission limits with files, while the guide's approach uses Claude Code in a terminal session on a dedicated Mac.

Continue Reading#

• Building SaaS with AI Agents in 2026: The Complete Workflow
• Using Claude Code for a Second Opinion on MRI Scans - What Actually Happened
• Does Code Cleanliness Affect AI Coding Agents?
• Claude Code Permissions: settings.json Allow, Deny, Ask - scoping what an unattended agent may run
• Claude Code Power User course - hooks, subagents, and headless runs for the unattended sessions this setup is built for

Sources#

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