Agentic coding - equipping LLMs with tools that can take action on your behalf - opens the door to a new mode of development: building from anywhere. With the right setup, you can start work on one device and continue on another, relying on persistent sessions to maintain continuity across them. I briefly introduced this idea in On working with agentic models and it warrants deeper dive. The goal isn’t to work more, but to lower the activation energy required to explore or iterate on ideas.
After experimenting with different tools and setups, I’ve landed on a workflow built on SSH, mosh, tmux, and Tailscale that lets me start something on my laptop, continue on my phone, and pick it back up on my tablet so long as I have a network connection.
This post walks through the evolution of that setup, what I learned along the way, and some of the unexpected impacts on my habits.
Here’s how it started.
My initial approach was to use TailScale and VibeTunnel to control Claude Code sessions running on my laptop from my phone while away from home.
The workflow that I’ve settled on, that works both when I’m away from home and when I’m at home but away from my desk, is to:
Anecdotal use case: if I’m nap-trapped by my sleeping infant, sending commands from my phone doesn’t disrupt her, whereas contorting to try typing on a laptop does.
About a week of trial and error was enough to validate the usefulness of the idea. But I also found that VibeTunnel’s browser-based interface introduces too much friction to the terminal typing and navigation experience. Especially with the release of Liquid Glass in the Apple ecosystem, where there is now added friction to simple actions like switching browser on iOS - unless you find and disable the Compact Tabs layout setting.