Live data from Hacker News

Herdr: One terminal to rule them all

herdr.dev

151–160 of 189 posts

Re: Herdr: One terminal to rule them all

#151

Earlier quoted context omitted.

If you do most of your work on a central server and treat your other devices as thin clients, then (afaik) Tmux/Zellij are the way to go – not to mention if you want to multiplayer with colleagues. (I know Wezterm has remote session multiplexing in beta, but I’d be surprised if you can re-attach from a different machine.) Lately I’ve been experimenting with embracing the total scriptability of my favorite terminal, K…

You might want to give https://github.com/kstenerud/yoloai a try, then. Runs agents in tmux in sandboxes.

Hard coded harness support... Yuck.

Gondolin is sand boxes done right...

Re: Herdr: One terminal to rule them all

#152

Earlier 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.

Say you have something easily paralelizable, like 150 decompiled binaries, and you want to produce documentation for what each does. You can run 50 subagents in parallel (eg. kimi swarm) to analyze it all in a few minutes in 3 batches instead of doing it serially which would take half a day.

Re: Herdr: One terminal to rule them all

#153

> Popular with engineers from... (bunch of logos) > Individual engineers, not company endorsements. Bold haha. Maybe that's fine with the disclaimer, but feels like lawyer-bait.

I've seen a lot of companies list logos if just a single engineer or team is using the product.

Feels like standard last ten years. All SaaS companies saying Used by people in Google just because one guy in support used it one time 5 years ago.

Re: Herdr: One terminal to rule them all

#154
post #84

I've been using tmux historically and it eventually became too cumbersome since my typical workflow started being a lot more AI-agent heavy. I now run over 10 agents at the same time and they're all working on some multi-hour workstreams that I occasionally need to check in on or unblock. Tmux was not making this particularly easy and I would occasionally lose an agent or forget about it until much later only to real…

I thought that was where I was going to end up, but that's where Claude's remote control or copilot's agents tab spared me. The hitching is compounded for me because I tend to run the agents in squads: the agent I talk to operates a strict no-coding 'producer' mode, it tasks a sub-agent to do the research or coding, then the results go via a file to a critic or review agent; keeps the producer context very minimal an…

I wish Claude's remote control sessions were longer running. If I forget about a conversation it's been cognitively difficult for me to track down which tmux tab = the correct remote control session in the Claude GUI. Remote control does come in super handy for pasting images in when some shell environments where pasting doesn't work for...reasons. The output in the GUI is also so much easier to read.

Re: Herdr: One terminal to rule them all

#155
post #148

Earlier quoted context omitted.

It's better than tmux. I've used both extensively, there's no reason to use tmux again.

Well, tmux is mature, battle-tested software, whereas probably no human has ever read the majority of the code in this project.

Would usuability (for what herdr is optimized for) not be the bigger use case for users?

I never heard of this project but in 5 minutes I got the features that I wanted without having to introduce muscle memory. I just wanted a dead simple way to point and click to select different terminals. The only thing I neeed to remember now is "ctrl-b + v" to create a new pane.

Re: Herdr: One terminal to rule them all

#156

Earlier quoted context omitted.

You might want to give https://github.com/kstenerud/yoloai a try, then. Runs agents in tmux in sandboxes.

Hard coded harness support... Yuck. Gondolin is sand boxes done right...

You don't have to use the opinionated harnesses. Nothing stopping you from launching your own.

Re: Herdr: One terminal to rule them all

#157
post #8

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 &…

I also quite like that it has a decent CLI and skill for agents to use too.

Quite handy to apply since you can instruct models to run devservers in herdr panes or workspaces rather than doing long running shell commands or scripts in the agent session.

(You could probably do the same with tmux and others but I've had better success with monitoring herdr state)

Re: Herdr: One terminal to rule them all

#158

I've been using tmux historically and it eventually became too cumbersome since my typical workflow started being a lot more AI-agent heavy. I now run over 10 agents at the same time and they're all working on some multi-hour workstreams that I occasionally need to check in on or unblock. Tmux was not making this particularly easy and I would occasionally lose an agent or forget about it until much later only to real…

In a multi-pane tabbed interface like cmux (I made my own), I found it sufficient for agents to always alert when they are done or awaiting my input, and then the tab shows a badge that counts the number of unacked alert panes inside it.

Then I just work through the alerts and handle them as they arrive.

I guess there's an edge case where you don't know if an agent is running in a tab at all (while herdr will show "Agent running") but in practice I'm the one starting agents, and they run until they alert, so I'm not hitting a case where I think an agent is running but it's not.

Re: Herdr: One terminal to rule them all

#159

Earlier 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.

Lower-priority backlog items. TODOs atop your new PRs. Code reviews. Exploratory work where you can discuss a design sync and then dispatch one or more agents to prototype async. Any workstream where you can define a loop and let the agent hill-climb towards the goal.

A lot of this is personal taste but the general thing I get most value from is asking an agent to speculatively build every idea, instead of writing down ideas in some backlog for later (it never happens later).

Post reply on HN