Your machines.
One command away.
Connect to development boxes across separate Tailscale accounts. Keep your sessions running, and your networks separate.
$ tailmux attach personal/devboxTailmux is a small Go CLI that brings your remote development machines into one workflow. Give each Tailscale account a name, choose a host, and connect using the SSH keys you already trust.
Start here
Install Tailmux
One binary. macOS or Linux. No root required.
Make your first connection
From a named profile to a remote shell in a few commands.
A profile, a host, a session
$ tailmux login personal
$ tailmux hosts
$ tailmux herdr attach personal/devbox
The names are yours. personal could be work, lab, or a client name. devbox is a hostname visible inside that account. There are no built-in accounts or machines.
A little less switching
Keep both accounts connected. Each profile has an independent embedded Tailscale node. Your system Tailscale connection keeps doing its thing.
Use familiar SSH. Tailmux transports the connection; OpenSSH handles your user, keys, and agent. That includes 1Password.
Bring your boxes together. Use tailmux herdr open for a local Herdr view with one workspace per host. Explore the combined view.
Run Orca on the boxes themselves. Connect native orca serve runtimes over Tailmux and keep their projects and agents remote. Orca runtimes.
Pick a box from your terminal. Use tailmux terminal with tmux or Zellij and a saved backend preference. Terminal & box picker.
Open remote apps locally. Forward a port or range to localhost, or use named HTTP URLs with redirect rewriting. Port forwarding & local URLs.
Leave work running. Attach to Herdr on a remote machine, detach, then pick up the same shell later. Your processes stay on the host.
Early development
Connection management, Herdr attachment, tmux/Zellij terminals, and port forwarding work today. Process picking and task dispatch are planned. The roadmap keeps that distinction explicit.