Mosh, Caddy & Tailscale: A Remote Dev Deep Dive  🔗 **Source:** [Mosh, Caddy & Tailscale: A Remote Dev Deep Dive]() ## Highlights - Once agents outlive a laptop session, development becomes an operated service rather than a local application. - Note: Persistent compute changes the developer boundary - DNS and device labels improve use; trust still depends on authenticated devices, users, and policies. - Note: Friendly names are not authorization - Closing the laptop shifts failure risk to power, network, storage, updates, and recovery on the host. - Note: Remote convenience spends reliability budget - The ability to prompt agents everywhere can erode boundaries unless teams define when remote work should stop. - Note: Mobile access needs a stopping rule