Keeping a Mac mini running at home and controlling it from your iPhone

A Mac mini is small, quiet and cheap to leave on, which is why so many end up in a cupboard or behind a TV doing a job: a home server, a build machine, a box that runs AI agents overnight. The trouble starts the first time you are out and need it to do something. You reach for your iPhone and discover that controlling a Mac mini from a phone involves more decisions than you expected.

This guide treats the Mac mini as what it usually becomes, an always-on machine without its own screen, and works through the three things that decide whether phone control is pleasant or frustrating: keeping it reachable, choosing how to control it, and surviving the day it restarts while you are away.

The Apple-only options, and their limits

People often ask whether there is an Apple way to do this with no third-party apps. There is a partial one.

On the iPhone, Settings, Accessibility, Control Nearby Devices lets the phone send controls to another Apple device. Apple's iPhone guide is specific about the conditions: the device you want to control must be signed in to the same Apple Account and connected to the same Wi-Fi network as your iPhone. The controls are buttons, such as media playback, not a view of the screen. It is useful when you are in the next room. It is not remote access.

On the Mac mini itself, macOS includes Screen Sharing and Remote Login, both in System Settings, General, Sharing. Screen Sharing lets another device view and control the desktop, and it can accept VNC viewers with a password. Remote Login turns on SSH. These are the building blocks everything else uses, but macOS does not ship an iPhone client for either. Apple Remote Desktop, the company's management app, is a Mac-only App Store listing at $79.99. So in practice, controlling a Mac mini from an iPhone means one Apple feature on the Mac side and one third-party app on the phone.

Keeping a headless Mac mini awake and reachable

A remote session can only reach a Mac that is on, awake and online. With no display attached, it is easy to forget that the Mac mini still follows its sleep settings.

Three settings matter, and all three can be checked with the pmset command, whose manual page lists them:

• sleep: the system sleep timer in minutes. A value of 0 disables system sleep entirely, which is what most always-on Mac minis want.
• womp: wake on network access. The manual notes this is the same as "Wake for network access" in System Settings. It lets some connections wake a sleeping Mac, but it is a fallback, not a plan.
• autorestart: automatic restart on power loss. Without it, a short power cut leaves the Mac mini off until someone presses the button.

Run pmset -g in Terminal to see the current values. If you only need the Mac awake for a specific job, caffeinate is lighter: caffeinate -s prevents system sleep while the Mac is on power, and stops preventing it when you end the command.

Network reachability is the second half. On your home Wi-Fi, the phone can see the Mac mini directly. On mobile data, it cannot, because your router blocks incoming connections. The common fix for a personal setup is a private network between your own devices. Tailscale is the tool most guides name; its pricing page lists a Personal plan at $0 with unlimited user devices and up to 6 users. With it installed on both the Mac mini and the iPhone, the phone reaches the Mac by name from anywhere, and every method below works the same way outside as it does at home.

Wired Ethernet is worth the cable if the Mac mini sits near the router. A headless machine you cannot see is not the place to debug Wi-Fi dropouts.

Screen sharing: when you need to see the desktop

If the tasks you do remotely involve graphical apps, you need screen sharing. Turn on Screen Sharing in Sharing, restrict "Allow access for" to your own account, and enable "VNC viewers may control screen with password" if your phone app uses VNC.

On the phone, the choices most often recommended for a Mac mini are:

App	Connection	App Store price	Relevant to a Mac mini
Screens 5	VNC and its own remote access	Free download	Listing mentions headless Mac mini setups, Curtain Mode and Tailscale integration
Jump Desktop	VNC, RDP and its own Fluid protocol	$14.99	Listing says no subscription
RealVNC Viewer	VNC	Free download	Plain VNC client

Curtain Mode, which the Screens listing mentions and Apple Remote Desktop also offers, is worth knowing about if the Mac mini is connected to a TV or monitor that other people can see. It hides what you are doing on the shared screen while you control it remotely.

Screen sharing is at its best for short visits: dismissing a dialog, restarting an app, checking a window. It is at its worst for reading long text on a phone, because you are looking at a shrunken desktop and scrolling constantly.

SSH: when the Mac mini's job is mostly the terminal

A lot of always-on Mac minis spend their lives running things in the terminal: scripts, servers, backups, and more and more often AI coding agents such as Claude Code or Codex. For that work, SSH is the better remote channel.

Turn on Remote Login in Sharing, again restricted to your account. Apple's guide to allowing remote access shows the basic form, ssh username@hostname, and the Sharing pane displays the exact command for your Mac. On the phone, App Store listings for Termius, Blink Shell and Secure ShellFish all describe SSH support, and Termius and Blink Shell also mention Mosh, a mobile shell whose site describes it as supporting roaming and intermittent connectivity.

Two habits turn SSH from workable into comfortable:

1. Use keys, not passwords. Generate a key in the phone app, add the public key to ~/.ssh/authorized_keys on the Mac mini, and confirm key login works before you rely on it.
2. Run long jobs inside tmux. Start the job in a tmux session on the Mac. From the phone, attach to that session instead of starting a new shell. When the phone locks or the signal drops, the job keeps running and you reattach later. Secure ShellFish's listing specifically mentions built-in tmux support for this reason.

The result is that checking on the Mac mini from a train means reading real text at a readable size, over a connection that barely notices weak signal.

Getting files off the Mac mini from a phone

Remote control and remote files are different problems, and phone apps solve them separately. Once Remote Login is on, the same SSH access carries files. Termius lists SFTP in its free Starter plan alongside SSH. Secure ShellFish goes further and says the server file system is available in the iOS Files app, with recently accessed files cached for offline use, which means other iPhone apps can open a document that lives on the Mac mini.

This matters because a screen sharing session cannot hand you a file. You can look at a document on the shared desktop, but getting it into an app on the phone means emailing it to yourself or putting it in a cloud folder from the Mac side. An SSH-based file route skips that round trip.

The same reasoning applies in the other direction. Dropping a photo or a note onto the Mac mini from the phone, so an agent or a script can pick it up later, is a file transfer, not a remote desktop task.

The day it restarts while you are away

This is the part that catches people. The Mac mini restarts, for a macOS update or after a power cut, and suddenly nothing connects.

If autorestart is off, the Mac is simply still off. Turn it on.

If FileVault disk encryption is on, a restart stops at the unlock screen before macOS fully loads, so neither Screen Sharing nor SSH is available until someone types the password at the machine. For a planned restart you trigger yourself, sudo fdesetup authrestart restarts and unlocks once. Its manual page warns that FileVault protections are reduced during these authenticated restarts, because the unlock key is kept in memory for that one boot. For unplanned restarts, there is no remote fix; you choose between the protection FileVault gives a machine that could be stolen and the convenience of a Mac that always comes back on its own.

Apps and jobs are the last layer. Anything you want running after a restart should start by itself, through a launchd job or the app's own "open at login" option, rather than depending on you to start it from the phone.

Notifications, or how you know something needs you

Phone control is reactive by nature: you connect because you decided to check. The setups that feel effortless add a push in the other direction, so the Mac mini tells you when it wants attention.

Three routes are common. A script can finish by sending a message to a chat service you already have on your phone, using nothing more than curl and a webhook URL. A terminal bell can be turned into a visible alert, which is useful when you are at the machine but not when you are out. And some tools that pair a Mac app with a phone app push a notification when a job finishes or a prompt is waiting, which removes the guesswork entirely.

Whichever you choose, the goal is the same: stop opening a remote session every twenty minutes to see whether an overnight job is done.

A setup that works for most people

Putting it together, a reliable phone-controlled Mac mini usually looks like this:

• Sleep disabled, automatic restart after power loss on, Ethernet if possible.
• Tailscale, or a similar private network, on the Mac and the phone.
• Remote Login on, key-based, with long jobs in tmux.
• Screen Sharing on for the occasional graphical task.
• A decision made in advance about FileVault and restarts.

If most of what the Mac mini does lives in folders and the terminal, there is a lighter alternative to juggling separate SSH and file apps on the phone. Some file managers with a built-in terminal now pair with an iPhone or iPad companion that shows the Mac's terminal as live, reflowed text and lets you browse the folders registered on the Mac, connecting directly on the same Wi-Fi and through an encrypted relay away from home. The iPhone and iPad page shows what that looks like, and the FAQ covers the common setup questions.

What to change first

Run pmset -g on the Mac mini and fix sleep and automatic restart before anything else, because no remote app can reach a Mac that is asleep or off. Then turn on Remote Login with a key and a tmux session, and add screen sharing only for the tasks that truly need a desktop. If you want the terminal and folders together on the phone, Atriens is one way to set that up.