Dev.to
7/27/2026

The original title is "How I Built a Persistent Remote Dev Environment and Updated My App From a Phone"
Original: I Updated My Android App From a Restaurant. My Laptop Was Off.
Short summary
The author describes a remote development setup where a home Ubuntu PC runs repositories, Docker containers, databases, and AI coding agents while a MacBook Air serves as a thin client via VS Code Remote SSH and Tailscale. This architecture enabled them to trigger code changes from an Android phone using Codex while the laptop was off, demonstrating that persistent remote infrastructure can outperform a local laptop workflow. The key insight is separating the development environment from the client device for continuity.
- •Home Ubuntu PC hosts code, services, and AI coding agents; MacBook acts as thin client
- •Tailscale and VS Code Remote SSH connect the machines over a private network
- •Codex on Android enabled code changes while the laptop was powered off
Generated with AI, which can make mistakes.
Is this a good recommendation for you?


