# Mosh, Caddy & Tailscale: A Remote Dev Deep Dive > [!question] Lingering Questions > - What's the actual completion-rate benefit of always-on agent hosts vs. laptop-bound sessions? The hosts supply no data, only the workflow description. > - Where does "remote convenience" cross the line into "erodes work boundaries" for someone who can now prompt an agent from any device, at any hour? > [!tip] Article Ideas > - A WordPress-agency threat model for an always-on personal remote-dev host: device approval, secrets exposure, backup ownership, offboarding. > [!link] Cross Reference > - [[3. Resources/Permanent Notes/Managed Hosting Collapses the Setup Friction That Gates Self-Hosted AI Agents]] — adjacent claim about the setup-cost side of self-hosted agent infrastructure > - [[3. Resources/Permanent Notes/An Ops Agent Is Only as Capable as Its System Access]] — the persistent-host discussion here is a specific case of that broader claim > [!quote] Vocabulary > - *Mosh* — mobile shell; a resilient terminal connection that survives network changes and sleep, unlike plain SSH. > - *Tailscale* — a WireGuard-based mesh VPN adding device identity and approval on top of raw peer-to-peer networking. ## Metadata - Source: [[3. Resources/Readwise/Articles/Mosh, Caddy & Tailscale A Remote Dev Deep Dive]] - Format: Syntax podcast/video, Scott Tolinski and Wes Bos. ## Author's thesis Long-running coding agents outlive laptop sessions, so moving development work to an always-on Mac mini or server — reached via Mosh, fronted by Caddy for HTTPS, networked with Tailscale, kept alive with tmux or Herder — can make remote development feel local while improving continuity, battery life, multi-device access, and realistic HTTPS testing. The tradeoff: this turns a personal laptop workflow into operated infrastructure that needs device approval, narrow access, encrypted storage, backups, monitoring, and a recovery plan. ## Key arguments (≤3) 1. **Agent work needs persistent compute.** Long tasks should survive laptop sleep and network changes; the hosts pair always-on machines with Mosh and persistent terminal sessions specifically to keep agents running unattended. 2. **Device identity beats raw network exposure.** Tailscale adds device approval and naming on top of WireGuard, which the hosts contrast favorably against either a bare WireGuard setup or a public tunnel. 3. **Convenience creates operations.** An always-on personal host quietly becomes shared infrastructure — reboots, process management, and remote availability are now things somebody has to own. ## Claim atoms ### Agent work needs persistent compute Claim: Long-running tasks should survive laptop sleep and network changes. Evidence: always-on hosts paired with Mosh and persistent sessions. Limit: no completion-rate data is supplied — this is workflow description, not a measured result. ### Private names improve development Claim: Stable HTTPS domains make mobile and secure-context testing easier. Evidence: Caddy maps domains to project ports and handles TLS automatically. Limit: certificate and DNS failure modes aren't studied here. ### Device identity beats raw exposure Claim: Tailscale adds device approval and naming around WireGuard. Evidence: contrasted directly against raw WireGuard and public tunnels. Limit: central Tailscale account compromise remains a single point of failure. ### Convenience creates operations Claim: An always-on personal host becomes shared infrastructure whether or not anyone planned for that. Evidence: the episode discusses reboots, process management, and remote availability as ongoing concerns. Limit: updates, backups, and offboarding are named but left underdeveloped. ## Permanent candidates - **Persistent compute changes the developer boundary** — supported by the "agent work needs persistent compute" and "convenience creates operations" atoms together; the through-line of the whole episode. → promoted. ## Processing checklist - [ ] Compare Tailscale preview domains against Cloudflare tunnels for the same use case - [ ] Add device-revocation drills to any developer offboarding checklist I maintain - [x] Connect into the relevant MOC — [[3. Resources/MOCs/AI & the Future of Knowledge Work MOC]] ## Links - [[3. Resources/MOCs/AI & the Future of Knowledge Work MOC]] — persistent compute as infrastructure for long-running coding agents