Your Laptop Is Just a Portal
My laptop is a four-year-old Dell XPS 15 with 16 gigs of RAM. Fine for normal work. Not fine for running Windows, WSL, a real codebase, a Claude session, and a browser at the same time. It came to a head over Thanksgiving last year, when I was accidentally on the road for three weeks and couldn't get serious work done. WSL on 16 gigs just exploded.
The first fix was offloading development to an EC2 instance. That worked, but the monthly bill kept climbing and the hardware was still anemic for what I actually needed. So I bought a remote dev box for the home lab and moved everything off the EC2.
That's the boring origin story. The interesting part is what the setup unlocked.
Tailscale Is the Load-Bearing Piece
The one thing that makes the whole stack work is Tailscale.
The simple version: everything I own ends up on a single private network. The laptop, the remote dev box, my phone, a few small agent boxes. I don't have to think about the residential IP, the NAT, the router, or what's actually reachable from where. I SSH by name.
ssh remote-dev from my laptop on home Wi-Fi works.
ssh remote-dev from my phone on cellular works.
ssh remote-dev from a plane on airline Wi-Fi works.
That's the trick. Once everything is reachable by name from anywhere, "which device am I on" becomes "which portal am I using." The work itself doesn't move.
The Laptop Stops Being the Work
Cursor on the laptop is just a remote SSH session into the dev box. Every panel I open, every file I edit, every Claude session I run as an operational partner, it's all happening on the dev instance. The laptop is rendering it.
If I'm at my desk and walk away to eat breakfast, my work is still there. If I leave the house, my work is still there. If I pick up my phone in a terminal app and SSH into the same box, my bash history is there. My in-flight Claude session is there. My open files are there. I'm in the same workspace I left.
That's the practical payoff. Continuity. The laptop sleeping, dying, getting lost, or getting replaced doesn't matter much, because none of the work lives on it.
What This Enables
Once the work is portable, two things change.
First, the hardware ceiling stops being whatever fits in a laptop. The dev box has 32 gigs of RAM and a real CPU. I can run multiple Claude sessions, a small kubernetes cluster, my own agent processes, and the project I'm working on, all at once, without anything thrashing. The laptop never had to be the workhorse.
Second, the device in my hand stops gating the work. Phone in the kitchen, laptop on the couch, desktop at the office, they're all the same surface. I can kick off a session from my desktop, walk away, attach from my phone on the porch, type a redirect with speech-to-text, walk back, and pick up where I left off. The friction of "saving" or "syncing" or "context-switching devices" is gone. Gloria Mark's research at UC Irvine found it takes an average of 23 minutes and 15 seconds to fully refocus after an interruption. Most of that cost comes from rebuilding context. If the context never left, the cost never gets paid.
This is the same reason AI workflows keep converging on persistent-context architectures. Once the state lives somewhere durable, the tool you reach it with becomes interchangeable.
You Don't Have to Buy Hardware
I bought hardware because I wanted to. Tailscale is free. The trick, putting the dev environment somewhere durable and reaching it from anywhere, works on a cheap cloud VM, an old desktop in a closet (maybe not that old), or even a laptop you leave plugged in at home with the lid closed.
The point isn't the mini-PC. The point is that as soon as the work isn't tethered to the device in your hand, you can start treating the device in your hand as disposable. That changes what "working remotely" actually means. The work doesn't go with you. You go to the work.
Related Content
