So I've tried to figure out why you might want to use this over Tmux, and essentially I think it comes to down to: - everything is mouse clickable - tmux style display-popups are used for friendly UI interactions everywhere - it has a UI for agents running in panes, with a cool status (idle/working) display - has opinionated defaults like automatic clipboard copy on mouse text select - makes nested sessions easier &…
Herdr: One terminal to rule them all
161–170 of 189 posts
Re: Herdr: One terminal to rule them all
#162Re: Herdr: One terminal to rule them all
#163There's the more traditional tmux/zellij way. I have a tailscale and mosh and a script where I can say something like "cw api do-this-feature" and it'll go into the folder of my api, create a worktree, and fire up claude code to use it (and another tab with lazygit and delta so I can do side-by-size diffs). And modified tmux's defaults so the session & window names are more targeted. Then can have it in Ghostty locally or Moshi (https://getmoshi.app/) on my phone. Moshi is basically a terminal for iOS but geared toward doing agentic stuff. Has a lot of shortcuts you can add for common commands of tmux, CC, can pinch to change font size, has a built-in diff tool, etc. Also has a small hook you can put in your agent so you get notifications on your phone. And it can directly open the particular tmux/zellij/herdr pane from that (has specific support for those three).
So that approach is nice in that you get full access to the harnesses, with no worries that a wrapper has a bug or doesn't support some new feature. But it still doesn't flow as well for me as a "real" wrapper does.
For the real wrapper approach, I started with Happy (https://happy.engineering/) and currently am using Happier (https://happier.dev/). Unlike Moshi, these are open source and basically control the various harnesses and have their own UI. Also have a relay so tailscale isn't necessarily needed, along with encryption in such a way that the person owning the relay can't decrypt the sessions. Happier even has a desktop app. Right now I'm running the dev version of Happier from source on my own machine w/ tailscale, with the testflight version of the app. There's various rough-around-the-edges aspects (and they're currently in the middle of a re-write), but it is nice to have a real UI with tabs for all your sessions, can click in to expand tool calls, to start a new session just select the harness, folder, type a new worktree name, etc and it starts going.
So I don't know. I like aspects of both of these and kind of depends on what I'm up to and my current mood. Nothing feels totally perfect yet IMO.
Re: Herdr: One terminal to rule them all
#164I get why folks use tmux/herdr, but I already use i3wm/Hyprland for window/workspace management, and want to have "shared first class windows" instead of dual binds of "super-based binds for i3 windows ... oh wait control-a based binds for tmux panes". Has anyone got a tool/setup that is tmux-like but the remote terminals/panes are all local/native windows?
ITerm2 has a really great tmux integration where you get native windows or tabs for tmux windows and the panes are really easy to interact with. Of course it’s macOS only but I use it on my MBP and ssh to attach to my tmux sessions from a secondary Mac (getting the same experience remotely) or my phone (without all the niceties, just normal tmux, but still usable)
Re: Herdr: One terminal to rule them all
#165Earlier quoted context omitted.
There is a whole page about this https://herdr.dev/compare/ For me the killer feature is the git worktree management. But in essence it is tmux on steroid (Specifically for agents)
I wonder if it works with jj workspaces as well. I guess I have something new to tryout today
Hopefully any of those get some traction
Re: Herdr: One terminal to rule them all
#166Earlier quoted context omitted.
I wonder if it works with jj workspaces as well. I guess I have something new to tryout today
Sadly it does not. There are both a discussion about support for non-git vcs ( https://github.com/ogulcancelik/herdr/discussions/522 ) and about jj specifically. Hopefully any of those get some traction
Re: Herdr: One terminal to rule them all
#167Earlier quoted context omitted.
I don't understand what it does. The homepage says it doesn't provide windows, panes or splits. What is it used for?
Provides a daemonized terminal basically, so you can attach and detach it freely. Other UI concerns are left to other layers.
Re: Herdr: One terminal to rule them all
#168Earlier quoted context omitted.
I think https://zellij.dev/ covers all of these? But it isn't an "agent native", and `herdr` seems to support importing existing agent sessions.
I use zellij a lot and created myself a zellij skill for an agent to manage my sessions/layouts in zellij directly. So for a new worktree the agent can create a tab in zellij with multiple panes, properly named etc. It works really nicely. Although since I got the 52 inch Dell monitor I tend to just put everything visible at all once most of the time.
Re: Herdr: One terminal to rule them all
#169So I've tried to figure out why you might want to use this over Tmux, and essentially I think it comes to down to: - everything is mouse clickable - tmux style display-popups are used for friendly UI interactions everywhere - it has a UI for agents running in panes, with a cool status (idle/working) display - has opinionated defaults like automatic clipboard copy on mouse text select - makes nested sessions easier &…
From what I can figure it is actively calling itself a multiplexer, so pretty closely linked to something like tmux (one of the review videos on the page calls it a "tmux rewrite"). But they seem to be targeting very different scopes use wise. I think if you use this to do stuff like, edit files, run htop, drop into an interactive shell, compile some code, my guess is you're gonna be fighting uphill and have a bad ti…
Re: Herdr: One terminal to rule them all
#170Earlier quoted context omitted.
Work.
What's an example of what the 10 agents would be doing in parallel? I've never used more than 2 in parallel before.
In practical terms it often means that you can give the agent a ticket and it'll work on it for several hours until the PR is ready. Occasionally it'll run into some question that it needs you to clarify something or make some directional choice, but overall it's pretty autonomous.
Because this takes so long, you normally run 3 or 4 of those in parallel.
Then between shepherding those session, you also run several PR review sessions at the same time. Those also run for quite some time when doing deep investigations.
And then you also have long running discovery/design sessions for various other projects or problems you're working in between.