For years my travel kit was a heavy laptop, a charger the size of a brick, two backup batteries, and anxiety about airport security lines. I would lose three hours of productivity every time I flew because my actual work lived on the machine in my backpack. Every time the machine went through a scanner, a battery swap, a reboot, or a hotel WiFi reset — my work stopped.
Today my travel kit is a 10-year-old ThinkPad T480S with a screen I paid $40 to replace, a charger that fits in a jacket pocket, and zero anxiety. Nothing important lives on the laptop. Everything important lives on a small always-on workstation I can reach from any internet connection with SSH. I call the setup "OpenClaw" as a joke. The idea is that my hands are free and the actual compute is somewhere else entirely.
This is not novel technology. Thin clients have existed forever. What's new is that AI agents have finally made the economics of this setup attractive for an individual operator. The networking layer that makes this practical is Tailscale — their documentation is the best primer on how to wire a personal mesh network with zero exposed ports. Here's the why, the what, and the how.
Why the thin-client model suddenly matters for founders
Three things changed in the last 18 months that made this setup actually practical for me:
- Long-running agents. I now have background agents monitoring for news, scanning for RFP opportunities, running reports, watching court filings (yes, I have court filings to watch). Those cannot live on a laptop that gets closed when I go through TSA. They need to live somewhere always-on.
- State management got serious. The gsd ecosystem and similar tools mean my work now has persistent state that lives in files. If those files live on a server, I can walk up to any machine, SSH in, and be exactly where I was. That's the force multiplier.
- Claude Code runs over SSH. I can do real AI-assisted development from a terminal on any machine. The heavy lifting happens server-side. The laptop is just a keyboard and a screen.
The actual hardware
The laptop is a ThinkPad T480S. I bought it refurbished for just under $200. Replaceable battery. Real keyboard. Working trackpoint. Roughly zero resale value, which means I do not panic if it gets stolen, damaged, or confiscated. It runs a plain Linux install. No important data on it. No cached credentials that could do damage if someone else booted it.
That is the whole point. The laptop is literally disposable. If it drops out of a bag in a taxi in Mexico City, I go to a shop, buy the next cheap laptop off the shelf, install Linux and an SSH client, log back in, and I'm working again in 30 minutes. Try doing that with a MacBook that has three months of uncommitted work sitting in local folders.
The server side
On the other end of the SSH tunnel is a small always-on workstation. The specs don't matter. What matters is that it has:
- Enough CPU and RAM to run Claude Code, a database, and several long-running agent processes at once
- A fixed IP and a domain I control, so I can reach it from any network
- SSH with key-based authentication only (following SSH key best practices), running on a non-standard port, with fail2ban and unattended upgrades
- Automated daily backups to a separate location I also control
That's it. No cloud provider lock-in. No SaaS subscription. No "agent platform." Everything is standard Unix. Everything is portable. If the server dies, I restore the backup to a new machine and I'm back in business the same day. Simple beats clever every time in infrastructure.
Your company's resilience is the sum of how many single points of failure you personally carry in your bag. Moving the state off your laptop is the single biggest resilience upgrade a traveling operator can make.
The travel kit that comes out of this
- The $200 ThinkPad
- A 65W USB-C charger (same one that charges my phone)
- A small mechanical keyboard I like because I'm particular about typing
- A pair of AirPods
- A SIM card for the country I'm landing in, usually bought at the airport
Total weight under 3 kilos. Total replacement cost if every single item got stolen tomorrow is under $500. My actual business — the agents, the files, the databases, the code, the contacts, the projects — is untouched, because none of it lives in the bag.
Where this setup fails
Honest disclosure. The downsides are real.
- Bad internet is fatal. If I'm on a plane without wifi, or in a coffee shop with 50kbps, I'm sitting on my hands. I've learned to batch work so I can be productive offline for short stretches, but this setup assumes reasonable connectivity most of the time.
- Video calls are a separate problem. I do those on my phone, not the ThinkPad. The laptop's webcam is terrible and the CPU struggles with modern video apps. Accepting that the laptop is not a video device was actually liberating.
- The setup curve is non-trivial. Getting SSH keys, shell aliases, tmux sessions, and agent state all working the way you want them takes a weekend of deliberate work. If you're not comfortable in a terminal, this setup will frustrate you.
Is this for you?
If you travel more than two weeks a month, if you run anything that needs to be always-on, and if you're comfortable enough in a terminal to live in tmux — yes. This setup adds several hours a week to your effective productivity and removes a category of travel anxiety you probably forgot you were carrying.
If you live in your home office and never go anywhere, the calculus is different. You probably just want a nice laptop and good backups. The thin-client move is specifically for founders whose calendar looks like an airline route map.
Here's the challenge. Next time you're about to board a plane, ask yourself one question. If this laptop got stolen at baggage claim tomorrow, how many hours — honest answer — would it cost me to be productive again? If the number is more than one hour, you're carrying a single point of failure in your bag, and you should spend a weekend fixing it. Not because the laptop is going to get stolen. Because the resilience upgrade is the real product of this exercise. The laptop is just the forcing function.
For the agent stack that runs on top of this hardware, see how I actually use Claude Code skills inside the operator's cockpit.