THE FIELD GUIDE
TAILMUX DOCUMENTATION

What's next

Available workflows and remaining work.

Available now

  • Interactive dashboard on tailmux, plus scriptable status output.
  • Arbitrary Tailscale account profiles with independent tsnet identities.
  • Cross-account host discovery, SSH settings and local/remote terminals.
  • tmux or Zellij with a box picker, saved backend preference and rename-safe tab routing.
  • Herdr attachment, session listing and a combined local view.
  • Native Orca runtime pairing, tunnel reconnection and reviewable user-service setup.
  • Remote prerequisite checks and explicit tmux/port-inspection package installation.
  • Remote TCP port/process discovery and forwarding from a picker.
  • TCP ranges, named HTTP routing, localhost redirects and saved forwarding groups.
  • Bounded SSH reconnection and saved-forward restoration at daemon startup.
  • Managed Cloudflare named tunnels and ngrok endpoints with an explicit public HTTPS origin.
  • macOS and Linux release tooling.

Still manual

Provider account authentication, stable domain ownership and Cloudflare DNS routing must be configured before publishing a public URL. Herdr and Orca application installation and provider-agent authentication remain separate. Orca firewall persistence and boot enablement depend on the host's firewall manager.

Saved forwarding does not install an operating-system autostart service. Private named routes require one-time local loopback setup; on macOS setup installs a LaunchDaemon that restores each alias at boot. A public URL routed through a laptop is unavailable while that laptop sleeps. Redirect rewriting does not change hardcoded frontend code or register OAuth callbacks.

Future: continuous process discovery

The ports picker takes a snapshot using existing SSH tools. Continuous monitoring and automatic forwarding as processes start would need explicit lifecycle rules.

Future: task dispatch

Create isolated checkouts and launch agents on a selected host. A cross-host handoff should transfer code and context explicitly; it should not pretend to migrate a live process.

There are no committed delivery dates. Current command behavior is documented in the CLI reference.

On this page