The 300-gram AI coding rig: iPad mini + Claude Code anywhere

#ai #claude #mobile #productivity

For the last two months, my daily Claude Code workstation has weighed about 300 grams.

Not the laptop. Not the desk. The whole thing — tablet, keyboard, the whole rig that I actually use to send prompts to Claude Code, watch the agent work, and ship code from a coffee shop. It's an iPad mini A17 Pro and a folding split keyboard, and I'm increasingly convinced this is the right shape of "AI coding workstation" for anyone who already runs an agent on a real machine somewhere.

I expected this to be a gimmick that I'd abandon after a week. It wasn't. So this post is the actual setup, the parts I use, and the one thing about iPad mini that I now consider a feature instead of a limitation.

What "AI coding from a tablet" actually means

Let me clear up the obvious confusion first: I am not writing Swift on an 8.3-inch screen. Nobody should do that.

What I'm doing is much narrower:

Claude Code runs on a Mac mini at home. That's where the codebase lives, that's where the agent has full filesystem and shell access, that's where the actual work happens.
The iPad mini is a remote control. I SSH into the home Mac, attach to a long-running tmux session, type prompts in plain English, and watch Claude Code do its thing.
My job is the prompt and the review. I read the agent's plan, I approve or redirect, I check the diff. The iPad mini is the screen and keyboard for that conversation.

When you frame it that way — typing intent and reading output — the screen size objection disappears. I'm not in a code editor. I'm in a terminal. Terminals scale down beautifully.

The exact rig

Here's everything I carry:

Item	Weight	What it does
iPad mini A17 Pro	~293 g	The screen and the brains for the prompt-and-review loop
Folding split keyboard (I use a 40-key split board, but any Bluetooth board with Ctrl/Esc works)	~200 g	Real keys, real Ctrl, real Esc, no soft keyboard pain
A small sleeve	negligible	So I can throw it in any bag

That's it. No hub, no laptop bag, no power brick. Battery life is a full work day even with continuous SSH.

The keyboard part matters more than people expect. Any iPad terminal experience without a real Ctrl key is going to make you miserable — every shell command needs Ctrl-C, Ctrl-D, Ctrl-R, and the soft keyboard's modifier handling is nowhere near good enough. A cheap split board changes the entire experience.

The software side

Four pieces:

Tailscale — free for personal use. Lets the iPad mini reach my home Mac mini securely from anywhere, with no router config or port forwarding. I cover the install in my Tailscale post (link will go here once that one is published).
An iOS terminal app — anything that does SSH and ideally Mosh. (More on this in a moment.)
tmux on the Mac side — so the Claude Code session keeps running even when my SSH connection drops. I have a four-command tmux primer if you've never used it.
Claude Code itself — installed on the Mac, started inside the tmux session.

The flow is:

Home in the morning  →  ssh into Mac, tmux new -As work, claude
                     →  ask Claude Code to do the long task
                     →  Ctrl+b d (detach), close laptop, leave the house

On the train        →  ssh into Mac from iPad mini, tmux attach -t work
                    →  see exactly what Claude Code is doing
                    →  answer its questions, redirect, approve

Cafe                →  same thing, different network — tmux + Mosh keeps it alive

Once this loop is set up, the iPad mini becomes a passive monitor for the agent. You're not even really "using" it most of the time. You give it a prompt, you go read a book, you come back when the notification fires.

The thing I didn't expect: the constraint is the feature

Here's the part of this setup that surprised me.

iPad mini is genuinely bad at multitasking. The 8.3-inch screen makes Stage Manager pointless. You can't really run a code editor and a terminal and a browser side-by-side. You do one thing at a time.

I assumed this would be the dealbreaker. It turned out to be the killer feature.

When my workstation is a MacBook with eight tabs open, I cannot stop context-switching. I check Slack, I check email, I look something up "real quick," I lose forty minutes. When my workstation is an iPad mini with literally no room for distraction, the loop is brutally simple: prompt the agent → put the device down → read a book → pick it up when something happens. I get more deep work done in two hours of iPad mini time than in four hours at my desk.

Single-tasking, when it's enforced by physics rather than willpower, is a productivity hack disguised as a hardware limitation.

What about the terminal app?

This is the part I struggled with for a long time, and the part that eventually made me build my own.

Most iOS terminals are fine for occasional SSH. They are not fine for the rig I just described. The pain points stack up:

Tap-tap-tap to switch tmux panes because the prefix key is hostile to touch
SSH dies the moment you switch from Wi-Fi to LTE on the train, and you lose your scrollback
No system-level notification when Claude Code is waiting on you, so you keep checking your phone

After about a year of duct-taping around all of this, I built MT — Mosh Terminal — a $14.99 one-time iOS terminal that has real Mosh (so the connection survives subway tunnels), one-tap tmux operations (no prefix-key juggling), and system push notifications wired into Claude Code Hooks (so the moment the agent needs me, my phone buzzes and a tap drops me back into the exact session). If the iPad mini rig sounds appealing but the terminal-app friction is what's stopping you, that's literally the reason MT exists. I'll write more about it in another post in this series; for now, just know it's there.

You don't have to use MT for any of this to work. Any terminal that can hold an SSH connection will get you started. The rig is the rig regardless.

Who this setup is actually for

Be honest with yourself before buying anything:

✅ You already use Claude Code (or Codex, or any agent CLI) on a Mac. This setup is a remote control for a workflow you already have. It does not make sense as a starting point.
✅ You like the "give it a task, walk away, come back" rhythm. If you need to be hands-on every keystroke, the iPad mini will frustrate you.
✅ You travel, commute, or hate being chained to a desk. Every hour I spend not at my main rig is an hour I'd otherwise lose.
❌ You want to write code by hand. Get a real laptop.
❌ You don't have a home Mac to SSH into. Tailscale + Claude Code on a remote box (a cloud VM, a Raspberry Pi, anything) works too, but you do need some always-on machine on the other end.

Wrap-up

The iPad mini AI coding rig is 300 grams of tablet, 200 grams of keyboard, four free or one-time-purchase pieces of software, and a workflow that turns "I need to step away from my Mac" from an interruption into a feature. After two months I have stopped reaching for my MacBook for anything that's just "talk to Claude Code for an hour."

If this resonates and you want the mobile-terminal half of the story, → MT — Mosh Terminal on the App Store.

I'm a solo iOS developer. I write about gadgets and dev tools at jaga-farm.com. MT — Mosh Terminal is my first App Store release. Find me on X at @jaga_farm.