# Persistent Compute Changes the Developer Boundary ## Claim Once coding agents outlive a single laptop session, development stops being a local application and becomes an operated service that someone has to run. <!-- atomicity: 1 idea ✓ --> ## Scope & conditions - Holds once a workflow depends on long-running agent tasks, always-available hosts, or multi-device continuity — the moment "close the laptop and it keeps working" becomes a requirement. - Breaks for workflows that stay session-bound: a laptop that's on while you work and off when you're done doesn't need operations, backups, or a recovery plan the way an always-on host does. ## Evidence The Syntax hosts describe a stack — Mosh for resilient shells, Caddy for HTTPS reverse proxying, Tailscale for device-identified networking, tmux/Herder for persistent sessions — built specifically so long-running coding agents survive laptop sleep and network changes. The same move that buys continuity also creates new obligations: reboots, process management, backups, certificate and DNS upkeep, and access revocation all become someone's job in a way they weren't when development lived entirely on one machine. ## Links - [[3. Resources/Permanent Notes/An Ops Agent Is Only as Capable as Its System Access]] — because extends; persistent hosts are the infrastructure layer that determines what access an agent actually has - [[3. Resources/Permanent Notes/Managed Hosting Collapses the Setup Friction That Gates Self-Hosted AI Agents]] — because contrasts; that note is about lowering the setup cost of self-hosted agent infrastructure, this one is about the operational cost that remains after setup - [[3. Resources/MOCs/AI & the Future of Knowledge Work MOC]] — because applies-in; long-running agent workflows and the infrastructure they require ## Tests / falsifiers - Track incident rate (missed backups, expired certs, revoked-but-still-active devices) on personal always-on dev hosts over six months. A low incident rate would suggest the operational burden is smaller in practice than the framing implies. - Compare agent task completion rates on persistent hosts vs. laptop-bound sessions for genuinely long-running work. If completion rates don't differ much, the core justification for taking on the operational burden weakens. ## Maintenance - Last tended: 2026-08-16 - Next review: 2026-11-16 ## Source - [[3. Resources/Readwise/Articles/Mosh, Caddy & Tailscale A Remote Dev Deep Dive]] — Syntax podcast/video, Scott Tolinski and Wes Bos.