Connecting the Machines

Published on September 7, 2026

The evolution of Herdr has reached a pivotal milestone: connecting the machines. With a growing ecosystem boasting over 700,000 downloads and nearly 1,000 community-driven plugins, Herdr has become a staple for those managing local machines and AI agents.

The Shift in Compute Philosophy

Previously, Herdr offered the --remote flag, allowing users to attach to a single remote instance. However, as agents evolve to run for several hours—or even days—the limitations of local hardware become apparent.

We rely on our laptops for all the heavy lifting. Instead, we are shifting toward a model where the laptop acts as a client, while the actual compute happens elsewhere. It is far more cost-effective to maintain a high-performance remote server than to spend thousands on a portable machine.

"The goal is to decouple the interface from the execution, ensuring that your work continues even when your laptop lid is closed."

The Problem: Tab Fatigue

Until now, managing multiple machines was a fragmented experience. If you had agents running across three different servers, you needed three separate Herdr clients, typically spread across different terminal tabs.

Why the delay?

Existing multiplexers like tmux or Zellij aren't designed for a single TUI client to manage independent servers across various machines. Herdr's architecture had to evolve. The challenge was avoiding a "master server" that aggregated connections, which would have created a bottleneck. Instead, the client now aggregates the views, while the servers maintain the sessions.

Implementing the Connection

You can now integrate a remote machine into your local environment using a simple command:

herdr machine add workbox

How it works:

1. Provide the SSH target.
2. The remote machine's workspaces, tabs, and agents are merged into your local Herdr TUI.
3. Persistence: Agents continue executing on their respective machines even after you disconnect.

Connectivity Options:

• Local Network
• Public Internet
• Mesh VPNs (e.g., Tailscale)

The Road to 1.0

While the TUI now supports multi-machine management, the agent CLI is still limited to a single server. The vision is to enable cross-machine agent collaboration, where agents on different servers can communicate and coordinate.

Future Milestones:

• Simplified Onboarding: Removing the need for manual SSH configuration.
• Herdr Cloud: A middleman layer to link machines via a single account.
• Security: End-to-end encryption for all terminal traffic.
• Session Migration: The ability to move a running agent session from one machine to another dynamically.

$\text{Total Experience} = \text{Unified TUI} + \text{Cloud Connectivity} + \text{Distributed Compute}$

If you are interested in the future of distributed agent management, you can join the Herdr Cloud waitlist.