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

Overview of “1023: Mosh, Caddy & Tailscale: A Remote Dev Deep Dive”

Wes Bos and Scott Tolinski dig into the growing trend of remote development workflows: running dev processes on another machine instead of your laptop, then connecting to it from anywhere. The core appeal is simple: keep long-running tools, AI agents, and browser tests off your main machine so you can close your laptop, improve battery life, reduce local chaos, and still access your full dev environment from any device.

They also walk through a practical stack for making this work smoothly: Mosh for resilient terminal access, Caddy for local HTTPS reverse proxying, Tailscale for private networking, Zed for remote editing, and Herder (a Tmux-like terminal multiplexer) for managing long-running sessions and agent status.

Why Remote Dev Is Becoming More Popular

The hosts frame remote dev as a response to how modern development has changed:

• AI agents often run as long-lived background processes
• Developers accumulate too many terminal tabs, child processes, and local services
• Laptops can get bogged down or need frequent reboots
• People want to access dev workflows from:
  • laptop
  • desktop
  • tablet
  • phone
  • other machines on the network

Main benefits they highlight

• Close your laptop without stopping work
• Better battery life and less local resource usage
• Access dev tools from anywhere
• Secure HTTPS/dev on remote services
• More flexible AI-agent workflows
• Cleaner separation between your machine and your dev environment

The Remote Dev Stack They Use

Mosh

• Used as the remote connection layer
• A drop-in alternative to SSH that reconnects automatically
• Great for closing/reopening laptops without losing your terminal session
• Requires Mosh on the target machine too

Caddy

• Acts as a reverse proxy and local web server
• Used to map domains like ai.robo.online to local services
• Provides HTTPS automatically
• Helps make remote services feel like normal web apps with real domains

Tailscale

• Connects devices together over a private WireGuard-based network
• Lets Scott name devices simply, like:
  • mini
  • NAS
  • MVP
• Makes it easy to connect via stable private hostnames instead of IP addresses
• Works well for keeping apps private to your own network

Zed

• Used for remote code editing
• SSH support makes it feel like editing locally even when files live on a remote machine
• Fast remote project browsing and editing
• One of the strongest “it just works” parts of Scott’s setup

Herder

• A terminal/session manager similar to Tmux
• Designed around remote dev and AI-agent workflows
• Features Scott especially likes:
  • multiple panes/tabs/sessions
  • persistent long-running sessions
  • agent status sidebar
  • easy visibility into whether an agent is blocked, running, or waiting for approval
  • plugins
  • clipboard behavior that automatically copies selected text

How the Workflow Actually Looks

Scott’s flow is roughly:

1. SSH/Mosh into a remote machine, often a Mac mini
2. Start projects normally from the terminal
3. Assign each project a domain through Caddy
4. Connect remotely with Zed for editing
5. Use Herder/Tmux-style sessions to keep terminals and agents alive
6. Run AI tools or browser automation against that remote setup
7. Access the whole thing from desktop or mobile when needed

The goal is for the remote environment to feel almost identical to local development.

Pros, Pitfalls, and Tradeoffs

Pros

• Cleaner laptop experience
• Persistent sessions
• Easier access from mobile devices
• HTTPS and secure origins by default
• Great for AI-agent workflows
• Private by default if you stay inside Tailscale

Annoyances / limitations

• Mobile terminal UX is still clunky
• Touch interaction in terminal apps isn’t great
• Browser testing/auth flows for agents are still awkward
• Some tools overlap heavily, making the space feel crowded
• Screen tearing / rendering weirdness can happen in Herder
• Agents and browser automation often still require manual intervention

Browser automation/auth

They discuss the difficulty of handling auth in headless/head-full browser workflows. Scott prefers seeing the browser open and watching the agent act in real time, but both hosts note that authentication and reliable browser control remain messy in this space.

Alternatives and Related Tools Mentioned

The episode also touches on the crowded “agent tooling” landscape:

• Portless as a Caddy-like alternative
• Cloudflare Tunnels as another way to expose local services
• WireGuard as the underlying protocol many of these tools build on
• Warp Terminal for agent status/UI features
• Solo, Conductor, Cursor Cloud, OpenCode, Claude Code, and similar agent tools
• Various “mux” projects:
  • cmux
  • gmux
  • dmux
  • wmux
  • muxy
  • smux
  • nmux
  • vmux

Their broader point: many tools are converging on the same problem—how to manage multiple AI agents, sessions, and workspaces cleanly.

Worktrees: When They Matter

They spend some time on git worktrees and where they’re useful:

• Good for trying multiple implementations in parallel
• Useful when multiple agents are exploring different approaches
• Less compelling for simple one-feature work
• Most helpful when you want to compare outputs or branch into several variations at once

Scott and Wes both seem to prefer simpler workflows unless the task really benefits from parallelism.

Sick Picks

Wes’s sick pick: Packing cubes

• Especially useful for travel and family packing
• Helps organize clothes by category
• Great for maximizing suitcase space and reducing chaos

Scott’s sick pick: Elgato foot pedal

• A three-pedal USB foot controller
• Used for:
  • push-to-talk dictation
  • Enter key
  • cycling through active agent sessions
• He likes that it’s powerful, configurable, and not ugly

Key Takeaways

• Remote dev is becoming more practical because modern workflows now depend on agents, persistent sessions, and background processes
• A strong setup can make remote work feel almost indistinguishable from local work
• The most useful stack in this episode is:
  • Mosh for reconnectable terminal access
  • Caddy for HTTPS and local routing
  • Tailscale for private networking
  • Zed for remote editing
  • Herder/Tmux for persistent terminal sessions and agent management
• The biggest unresolved issues are still mobile UX, browser auth, and tool sprawl