← All posts
November 19, 2026·6 min read·Henry — Kerber AI

SSH into Mac from iPad, without the cloud

Apple ships no Terminal app on iPadOS. Not in iPadOS 26, and not in iPadOS 27 either. The Mac has been shipping one for twenty years. So the shell you want on the iPad lives on the Mac, and the whole question is what stands between the two devices.

The phrase people type is SSH into Mac from iPad, and the intent behind it is small and reasonable: a working terminal, pointed at your own machine, with no ceremony around it. The default answer in this category is an app plus an account, and your keystrokes travel through a vendor's relay to get home. We ship the other answer. This note is the reasoning for it: what TermAway connects instead, what stays on your Mac, and what the choice costs.

TermAway is a Kerber AI venture, live at termaway.app and open source under MIT at github.com/alexkerber/termaway. The product claims below come from the product's own pages, its support page and our ventures page, read on November 19, 2026. No new experiment was run for this note. Where the note argues rather than describes, it states a design position, not a product promise.

The category's default shape

A terminal that reaches your Mac most often does it through someone else's machine. The iPad talks to a vendor's cloud. The vendor's cloud talks to your Mac. That shape exists for reasons: a relay reaches your machine from any network without router settings, it carries sync between devices, and it turns a hard problem into somebody else's problem. The price is that a third machine now sits inside your terminal session, one you neither operate nor patch.

The ventures page carries our one-line version of this: remote terminal apps route through cloud servers, and TermAway connects the iPad to the Mac directly. The distance between those two sentences is what the rest of this note walks through.

A server in the menu bar, a client on the iPad

Installing on the Mac gives you a menu bar app. Starting the server is a click, and that server is the product's entire footprint: shell sessions live on your machine, and they answer on the network because you started them. The iPad installs a native app with SwiftTerm rendering and a toolbar built for touch: Ctrl, Alt, Esc, Tab and the arrow keys are always one tap away.

Finding each other is Bonjour's job, so on your own Wi-Fi the Mac shows up by itself. A browser works too, at http://your-mac-ip:3000, for the day the native app is not at hand. The support page states the transport plainly: on your own Wi-Fi, TermAway runs entirely over your local network, with no internet or TermAway account required. And what opens at the other end is a full PTY, a proper shell with environment variables and tool support, not a chat window with a terminal skin.

The door faces inside

An open terminal is a responsibility, so the design keeps the exposed surface small. TLS can be enabled for LAN connections, a password gates access to the server, and terminal data never passes through any TermAway infrastructure, because there is none: the product's servers are your servers.

Reaching the Mac from outside the network is where a relay model usually earns its keep. The answer here is Tailscale: both devices join one private network, and no port forwarding exposes anything to the public internet. Tailscale connects the two devices directly when it can, and when it cannot, it relays end-to-end encrypted traffic over WireGuard through its own servers. The relay cannot read what crosses. TermAway still operates no server anywhere in that chain.

Sessions that survive a server restart

Terminal work has a recurring catastrophe: the long job that dies because the connection did. TermAway has an answer with tmux inside it. Out of the box, a session lives inside the server: stop the server, or restart the Mac, and the shells inside it end. Turn on persistence and each session runs inside tmux instead. In that mode the connection can drop, the server can stop and start again, and the long build or the running agent is still there when you get back.

The product's own configuration table draws the exact edge: persistence keeps sessions across a server restart, not across the Mac restarting, because the tmux server is itself a process on the machine. The support page adds the detail that matters in practice: the buffer that replays recent output on reconnect lives in the server, so after a restart it starts empty. Your processes survive; you reattach to a live screen, not to a log of what happened before.

The value climbs once the terminal carries agent hours. We have argued that the cost of a completed job is the number to measure, and a job that dies at minute fifty is one you paid for and never received. A session that keeps running while the devices around it do not is not a nicety in that world. It is how the job finishes.

What runs in the terminal now

One click installs hooks for Claude Code and Codex. When an agent finishes or waits for an answer, TermAway flags the exact session it runs in. It looks like a small feature, but it decides what the iPad session is: a place where agent work waits for your answer, or a place where agent work finishes without you.

Two field notes meet here from the other side. One is our argument that an agent's work trace deserves storage as evidence: a flagged session is another way of recording that something happened. The other is the rule that an alert is an interface problem as much as an agent problem, where Vigil draws its line: the loop closes when a human is pulled in with context. A notification naming the exact session is the same argument, arriving from the keyboard side.

Persistence plus agents is a combination with history in this studio: our agents once all triggered at once when a fallback chain unwound. A session that keeps running is a good thing only with that lesson attached. The photo button is the calmer example of the same wiring. Screenshot the bug on the iPad, tap the button, and its path lands in the prompt; the image is on your Mac already, because it crossed your own network.

What the no-cloud version costs

The trade deserves stating on the same page as the benefits. A relay account follows you to whatever machine you install this week. TermAway's server follows the Mac, and that has edges: the Mac has to be running for anything to reach it, and arriving from outside the network means installing Tailscale on both devices first. That is one more account in the design, free for personal use, but someone else's.

And a gap in the feature list cannot be filled by a roadmap promise. It is filled by reading the source: the whole thing is MIT licensed and sits on GitHub. You do not have to take the privacy paragraph on faith. You can compile it.

Setup stays at three steps, the menu bar app on the Mac, the native app on the iPad, one session to open. For a studio that runs several products, TermAway is the one designed to live entirely on hardware you already own. Where it sits next to the rest is on the ventures page.

Want more? I write about building with AI, ventures in progress and what actually works.

No spam. Unsubscribe any time.

Related posts