1023: Mosh, Caddy & Tailscale: A Remote Dev Deep Dive

This section discusses why developers might choose to run their processes on machines separate from their main workstation, such as laptops. Benefits highlighted include the ability to close laptops while processes run on a remote server, which conserves battery life and keeps long-running tasks alive without interruption. The hosts mention issues like frequent reboots caused by rogue processes and background apps, as well as new Mac OS features that support automatic reboots in case of power failures. Remote development also allows access to processes from any device, including phones and tablets, and facilitates secure HTTPS in development environments. Overall, the conversation emphasizes flexibility, better resource management, and continuity of work across devices.

The hosts elaborate on their tech stacks and recommended tools for effective remote development. Scott discusses using Mosh as a replacement for SSH for improved connection stability. Caddy is used for serving and routing domains securely with HTTPS, and Tailscale is highlighted for creating a secure, private network connecting all devices via WireGuard protocol. They discuss alternative tools like Portless, Cloudflare Tunnels, and other VPN options, but emphasize the stability and user management features of Tailscale. For editing, Wes praises Zed for its smooth remote setup, while Scott mentions using terminal multiplexers like Herder and Tmux for long-running or multi-session workflows. Additional tools include Termius for mobile SSH connections, with a focus on managing AI agents and development environments across multiple devices.

This section covers the variety of tools used to manage terminal sessions remotely. Scott and Wes share experiences with Tmux, Herder, and Warp Terminal. Wes appreciates Herder's ability to show agent statuses and manage multiple sessions through a visual sidebar, which helps keep track of multiple long-running agents and processes. They discuss the importance of having persistent, long-lived sessions to avoid losing progress when disconnecting or rebooting. The conversation also touches on mobile terminal applications like Termius and Termius for mobile, and challenges of interaction such as touch control and session management on mobile devices. They explore the difficulties of mobile workflows, frustrations with current solutions, and potential future improvements while emphasizing the need for seamless and reliable remote session management.

The discussion extends into headless browser automation, particularly for testing and AI interactions. Wes mentions using headless Chrome via Puppeteer, noting the challenge of avoiding detection as a bot. Scott discusses managing browser-based testing in development environments and potential issues with authentication. The hosts also explore challenges of running browser tests in headless mode, and how AI agents require managing secure, authenticated sessions. They mention the complexity of browser automation, Google’s measures against bot detection, and tools like cloud-based browsers versus local headless browsers. The segment highlights ongoing difficulties in working seamlessly with browsers and AI in remote setups, emphasizing the importance of reliable and secure authentication and the limitations of current headless browser solutions.

This section delves into the concept of work trees and their utility in AI-assisted development. Wes admits limited use but recognizes their benefit when exploring multiple approaches or implementations of features, especially for testing different models or algorithms simultaneously. They discuss tools like Demux.ai that enable managing multiple, isolated work trees, allowing parallel development and testing of different AI strategies. The idea is to control different branches for experimental work or various models, making it easier to compare and select the best approach. The conversation touches on how work trees can isolate different ideas, help manage costs in token-based AI development, and streamline the experimentation process.

The hosts consider options for hosting remote development environments, ranging from dedicated hardware like Mac Minis to cloud servers. They discuss the advantages and disadvantages of managing local versus cloud-based environments, including cost, control, and ease of management. The importance of fast internet connections and low latency for remote tools is emphasized, as many operations depend heavily on network performance. Scott mentions using a refurbished Mac mini, while also considering cloud providers like DAX and EXE.dev for cloud hosting. They highlight that local solutions can reduce costs and increase control, but cloud options might be better for scaling or if local hardware isn't available. Overall, they recommend balancing performance, cost, and control when choosing hosting options.

The episode wraps up with the hosts sharing their favorite tools and tips for remote development workflows. Scott highlights packaging cubes as a surprisingly effective organizational tool for travel, while Wes recommends using a foot pedal for macros and hands-free control, which enhances workflow efficiency. They reflect on the importance of experimenting with new inputs and workflows, especially as technology advances in developer tools. The discussion emphasizes flexibility, combining various tools for optimal remote development, and staying agile to adopt new innovations that improve productivity.