Herdr has released native app

Herdr, an open-source terminal multiplexer built around AI “coding agents,” has released a native desktop app, prompting comparisons to long‑standing tools like tmux, Zellij, Orca, and emerging rivals such as Rex. Users praise Herdr’s agent awareness, remote session management, libghostty-based rendering, and customizable UI “recipes,” saying it simplifies coordinating multiple agents and machines across projects. Skeptics are wary of its VC backing, telemetry defaults, and potential fragmentation between the new app and the original TUI, raising questions about long‑term monetization, lock‑in, and whether it offers enough beyond traditional terminals plus existing agent tools.

Overall reception

  • Many commenters use Herdr daily and describe it as polished, stable, and a productivity upgrade over tmux and other multiplexers.
  • Others tried it briefly and returned to tmux + Ghostty or existing setups, saying the benefits didn’t justify learning a new tool.
  • Several people say the marketing copy is confusing or “vibey” and doesn’t clearly explain what it does.

Compared to tmux, Zellij, Orca, etc.

  • Herdr is seen as more user‑friendly than tmux, with saner defaults, mouse support, and better handling of agents.
  • Some report friction or missing features vs. tmux (custom shortcuts, pane moves between tabs).
  • Zellij is praised but some had selection/copy issues; tmux can be extended with plugins to get similar agent awareness.
  • Orca is considered heavier/slower (Electron); Herdr is perceived as lighter (Rust + libghostty).

Agent‑centric features & workflows

  • Core value: Herdr knows which panes are agents, their status (idle/working/waiting), and surfaces them in an “agent inbox.”
  • Agents can control panes (read, send input, spawn others), making cross‑harness orchestration easier.
  • Strong focus on multi‑project, multi‑worktree work: workspaces, agent-aware navigation, and automatic reconstruction of setups after reboot.
  • Some argue tmux + notifications + harness features already cover most of this.

Native app vs TUI / architecture

  • New native app builds on a “herdr-core” engine; some are confused/worried about fragmentation and compatibility with existing TUI sessions.
  • The app adds a richer UI, diff/commit tools, and highly customizable layouts via JS-based “recipes.”
  • Some still prefer the TUI inside Ghostty and don’t see the need for another desktop app.

Remote, multi-machine & mobile

  • Native remote support (over SSH/Tailscale) is a major draw: unified view across multiple machines, easy reconnection, copy/paste and file handling.
  • Mobile access currently relies on third-party clients (Collie, Heeler, cosyra, relays); several want an official mobile app.

Funding, monetization, and data

  • VC and YC backing triggers concern about future “enshittification,” lock‑in, and pressure toward cloud upsell.
  • Others counter that open-source licensing enables forking and that donations alone weren’t sufficient.
  • Monetization is expected via “Herdr Cloud” as a connectivity middle layer.
  • Telemetry is on by default but claimed to exclude terminal contents and file names; can be disabled.

Open questions / criticisms

  • How well it supports self‑hosted models, containerized agents, and non‑agent workflows is unclear or partial.
  • Some see it as “fancy tmux”; others view it as a distinct “tmux for agents” sitting above existing harnesses.