Its intended as a terminal agent orchestrator aimed at power users who want a little more design than what I like to call 'hackerman' UXes.
The first app in this space was VibeTunnel[1]. It basically lets you start terminals on your Mac and the web app allows you to control these terminals on your iPhone using Tailscale. In the end, it’s just terminals on the web with organization around it.
I forked VibeTunnel and turned it into a Next app and added workspaces with memory and turned it into a software factory which is making open-source alternatives for me while I sleep. I call it VibeGhost and will be launching it soon[2].
0. https://opensource.builders/alternatives/conductor
- Paseo (https://github.com/getpaseo/paseo)
- t3code (https://github.com/pingdotgg/t3code)
Frankly I don't know a single person who does all this extra meta-agentic customization that gets anything done. You all are like the people who do nvim configurations all day and think they're being productive.
They are copying proprietary SaaS solutions and releasing them as opensource, at least according to what I understand from https://openship.org/
For Openship, the end goal is a decentralized marketplace.
This ethos goes into more detail
So an opportunity to learn the Bitter Lesson [1].
If tmux is good enough for people today, it should be good enough for agets tomorrow. That gap might comprise a beachhead. But you'd better scramble off the shores onto something more defensible fast.
[1] http://www.incompleteideas.net/IncIdeas/BitterLesson.html
Also, herdr is just an open source project with no VC capital behind it. So I don't think it needs to scramble to something more defensible. It can live a happy life pleasing users and then fade into obsolescence.
tmux is good enough for agents today. they're great at driving it, they're great at customizing it, what's the problem people have with it? i am confused.
This aged like milk!
I understand it has the agent pane on the left that tells you what is running but... that's it?
Realistically, what I use about its agent stuff is:
- reliable notification pings either via what your terminal app uses (e.g., ghostty's) or system or just within herdr only
- if absolutely necessary, be able to tell agent sessions to observe and run commands on a herdr pane (security beware, for obvious reasons)
- herdr --remote which is basically a quick SSH -> attach to herdr on a remote
- prefix+g (equivalent to prefix+w in tmux) presents itself nicer, has binds for agent state filtering and its /search imho is mildly nicer than tmux's
Arguably, you can have the same points in others if you know how to configure tmux or zellij already, so if you're comfortable with that then you really don't have to use herdr.
Herdr holds potential in stuff like their socket API ( https://herdr.dev/docs/socket-api/ ) and whatever enhancements they wish to bring (e.g., https://herdr.dev/docs/agent-automation/ ) so if that appeals to others, it's worth a shot.
But for most regular users, tmux and other multiplexers work just fine.
It’s fine.
When running many agents something like the “idle/working workstreams” gutter is honestly helpful though.
I rebuild herdr from master every few days to gauge the direction it’s moving in.
What herdr gets right over zellij:
- Default keybinds don’t conflict with helix. Even the leader key mode in zellij keeps alt-bindings around. Herdr keeps things nicely tucked away.
- There’s beta support for the kitty image protocol. Three years on, we’re still waiting in zellij.
- Notifications get passed correctly through to the terminal.
As for herdr’s killer feature, agent status monitoring, there is apparently a zellij plugin.
Big win for zellij: the docs and code feel human. By contrast, herdr’s docs have all the tells of a vibe coded project. Not to say the maintainer hasn’t put care into it! But I’m getting burned out on LLM docs.
To even get started with tmux you need to invest days to learn the keyboard commands. And yes good luck merging windows.
I can’t wait to forget all of the useless cli crap that Unix forced me to learn because nobody gave a damn about ux.
Overall I think I don't even want to start coding too much on the go with a setup like this but it's nice to have options :)
It does capture a provenance graph for any ad-hoc shell commands executed in the shell mode, or if prepended by `sci run`, by tracing all new files created from commands, and creating an accompanying json file for every output with metadata, which can later be assembled into a graph specific to any output file, using the `sci tohtml` or `sci toshell` commands (producing an HTML report with an SVG graph, or a reproducing shell script, respecively).
I'm quite bullish of the possibilities with this approach.
And, this was in fact also born out of the thinking to "rip apart" workflow tools, and build them up again using small, well-defined tools that do one thing well.
I'm working this with https://boxes.dev - a workspace for launching and managing claude + codex sessions, each running in its own cloud devbox.
We launched with a desktop app but have gotten a lot of pull for terminal-driven workflows, so have a TUI as well. It's interesting - when the Codex desktop app launched I was so sure that GUI is the future for coding agents (it's just a chat!). But turns out there's no killing the CLI
I do like having a permanent, remote workbox, but am a lot less keen on the idea of ephemeral boxes unless you're a company willing to invest into that infra.
If linux, can you name 1-2 advantages the desktop has over the terminal?
- drag and drop
- show document type, icon and filename
- inline images
- variable fonts, esp. monospace for code blocks
So GUI is mainly about readability. CLI works fine too but is inherently limited. I think GUI agents will keep pushing further in information layout, rendering, retrieval and interactivity. We're just at the beginning of it.
The only advantage of the terminal is that it’s easier to use on remote machines. I can’t think of anything else, even the usual benefits of composing commands is not relevant for a CLI like Claude Code.
- pi-web (https://pi-web.dev/): a web frontend for the Pi coding harness which can multiplex pi sessions across multiple machines
- herdr (https://herdr.dev/): a fairly polished agentic multiplexer TUI, can easily spawn or destroy windows based on subagent activity
- firstmate (https://github.com/kunchenguid/firstmate): a meta environment for coding harnesses - more naturally handles spawning and communicating with subagents, managing worktrees, and other SDLC functions, and has a fairly large number of constraints thru bash scripts to ensure better results with less intelligent models