The deceiving logo marquee is the most annoying thing of this software era. "Popular with people that follow these companies on social media" is the next step to this madness.
Herdr: One terminal to rule them all
101–110 of 189 posts
Re: Herdr: One terminal to rule them all
#102Herdr did a lot of things really well.
It have a great landing page where you can see and interact, and that really made me try it, and a few of my friend was also captured and immediately understood what it is for. I basically do everything remote, never on my own machine.
Once I tried it, I can never go back. It is so simple and worked exactly as I thought how it should work.
I would say it is just a modern version of tmux but really thought about user experience of more novice users. For people who come from the mouse world, moving to this is quite seamless.
Also, coming to the comments, I would think maybe `zellij` would also work well. Or use `zmc` and build something on top. `zmc` is great, as the then the tab/window management can be handled by the desktop or TUI, depend on what someone want to use.
Re: Herdr: One terminal to rule them all
#103Earlier 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.
Not the above person, and I usually max out around 5 although I have definitely had 10 or more at some point.
Assuming I'm working on one repo, I'll have different worktrees, each for a related area. For example, one worktree for each of: ui, small bug fixes, feature A, feature B, and so on.
Each worktree will have one active write agent, but I have a special docs/plans folder where I can have additional agents doing research and saving their findings. Agents in "plan mode" are write restricted to just that folder.
So look at a bug fix worktree. I could easily have 5 agents doing RCA into various bugs, each in plan mode. One at a time will get promoted to write mode to fix its specific bug while I continue discussion/RCA with the others. After fixing several bugs I'll spin up a "quality pass" agent that will make sure all tests/lint etc. pass and then give me a list of touched surfaces to manually verify before merging the branch and closing the worktree.
Note, I'm working solo at the moment so there's no PRs needed, but it would look quite similar if I had to make a PR for each bug fix, just probably with more worktrees.
Re: Herdr: One terminal to rule them all
#104[flagged]
Re: Herdr: One terminal to rule them all
#105I 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?
Something like this would be great. It seems what one really need is just persistent terminal session. So this thing probably can be built on top of zmc with a few scripts.
Re: Herdr: One terminal to rule them all
#106I have created my own opinionated setup but this comment is not about that.
I do think that there should be a protocol such that using these tools becomes more standardized.
For example I know that cmux is trying to support a tmux based setup so it feels like tmux could be most of that protocol.
There are a lot of tools like this popup and I really think making switching easier is the only way I will try a different tool.
Re: Herdr: One terminal to rule them all
#107Re: Herdr: One terminal to rule them all
#108So 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 &…
You missed the most important one. Automatic git worktree management. So that different agents don't clash with each other.
Re: Herdr: One terminal to rule them all
#109I just want the sound notification when they are blocked/done.
Re: Herdr: One terminal to rule them all
#110I still don't fully get the additional value over tmux, beside notification regarding the agent status?
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)