Live data from Hacker News

Herdr is joining Y Combinator. The runtime stays open

herdr.dev

121–130 of 197 posts

Re: Herdr is joining Y Combinator. The runtime stays open

#121
post #119

A nice little asciinema demo would be helpful on the TUI page. I should be able to see what it is, how it presents the contained agents, etc. I've been evaluating a few of these (and built one into another project I was working on, almost by accident), and am mostly looking for a frontend agnostic, terminal only (not harness) which can submit instructions to agents one line at at time with rate-limiting. I was also s…

in the herdr homepage near the top there is an interactive demo that responds to your mouse clicks

Re: Herdr is joining Y Combinator. The runtime stays open

#122
post #12

I switched from tmux to Herdr about six weeks ago. It's a great bit of software, the UI is focused on switching between multiple agents quickly. I run Herdr to keep my opencode instances well managed, and it also works great for having a few terminals opens next to your agent. I find myself keeping opencode sessions open for longer like what happens with Codex and Claude code, which is great if I need to revisit a co…

What made you prefer it to tmux? Looking at their demo, they put a lot of emphasis on the workspace like feature which tmux already got with sessions. Not sure what is the point of all those new tui runtime, tried a few but always got back to tmux, what am I missing?

Re: Herdr is joining Y Combinator. The runtime stays open

#123
post #12

I switched from tmux to Herdr about six weeks ago. It's a great bit of software, the UI is focused on switching between multiple agents quickly. I run Herdr to keep my opencode instances well managed, and it also works great for having a few terminals opens next to your agent. I find myself keeping opencode sessions open for longer like what happens with Codex and Claude code, which is great if I need to revisit a co…

What made you prefer it to tmux? Looking at their demo, they put a lot of emphasis on the workspace like feature which tmux already got with sessions. Not sure what is the point of all those new tui runtime, tried a few but always got back to tmux, what am I missing?

What you’re missing is the status updates. Herdr applies pattern recognition to detect the status of an agent running inside, so you get updates on all your agent threads at a glance.

Re: Herdr is joining Y Combinator. The runtime stays open

#124

I've been using Herdr for a while now, but I'd like a multiplexer that's also a meta-harness that I can connect to remotely. I know others have setups that work, I just haven't quite figured it out yet.

My same line of thinking and apparently of several others, turns out herdr has a plug-in for this: https://github.com/nikok6/herdr-mirror which is close to what I need.

Re: Herdr is joining Y Combinator. The runtime stays open

#125

Congrats to Can on the pre-seed funding. genuinely wishing you all the best. The terminal multiplexer / multi-agent coding space is getting very crowded. YC alone has funded many competing startups in this space: herdr, Superset, cmux, Emdash, Orca, Bullet, Conductor (Conductor was in YC before pivoting from chat->coding). I’m probably missing a few, and that’s before counting companies outside YC such as Superlogica…

For me, Open Source is extremely important because the tools are rapidly changing, and for reasons unrelated to my productivity. I use Copilot CLI at work, but now have a daemon that monitors it for updates and monkeypatches in my own custom hook framework.

This came about after 3 separate incidents where I went to use the harness and found it now provided a degraded experience because Microsoft unanimously decided to change some part of it without my consent.

I am a staunch believer that the most important thing a tool can do, other than its job, is provide a static experience until the user opts to change it. I use AI like a tool, because it is. I need it to behave the way I expect, or it's not actually useful to me.

Re: Herdr is joining Y Combinator. The runtime stays open

#127

Earlier quoted context omitted.

But it’s not only toxic to the greedy corporations but all the others as well, hence

Why is it toxic for me to need to push my code to a git repo if I start using it in my services, if I'm not trying to act as a for-profit corporation?

AGPL says nothing about pushing code to repos.

Re: Herdr is joining Y Combinator. The runtime stays open

#128
post #48

Earlier quoted context omitted.

Over the last year I ended up duct taping a lot of functionality onto tmux to get what these new age multiplexers set out to do (session launch, live agent status, etc). And it works, but it definitely feels like duct tape. I'm not sure the tmux project wants to evolve to support this natively so for now herdr seems like one of the best open and forkable options available. Considering how little I've had to really to…

I've been wondering what the point of a lot of these new multiplexer projects are when tmux is so extensible. I'd be curious to see eactly what you've done. Care to share a tmux config?

It's less the tmux config and more the scripting around it.

(shameless plug: I launch agents in tmux directly into docker containers with remuda, a tool I built at work & open sourced [0])

Anyway, I have a vibe coded script that shows me this overview for each of the agents I launch in tmux (hope this doesn't turn out mangled):

  ╭───────┬───────────┬────────────┬─────────────┬───────────────────────────────────────────────╮
  │ AGENT │ PR        │ REPO       │ BRANCH      │ ISSUE                                         │
  ├───────┼───────────┼────────────┼─────────────┼───────────────────────────────────────────────┤
  │ ready │ draft   │  │ branch1     │ Fix data race in e2e mock AssertExpectations  │
  │ ready │           │  │ branch2     │ Modernize such and such                       │
  │ ready │ open    │  │ branch3     │ JIRA-123: some sprint work                    │
  ╰───────┴───────────┴────────────┴─────────────┴─────────────────────────────────────────────-─╯
The agent status column (ready/working/etc) is just using heuristics from the terminal title (since a lot of harnesses have the live status in the title) or tmux capture-pane

The rest of the fields are either the gh cli or from beads, detected from the branch name (using https://github.com/Dicklesworthstone/beads_rust).

My session switcher is cool (shows the session name and the issue title + a preview of the issue details) but ultimately also along those lines; tmux itself doesn't do a whole lot, it's just being extensible and letting me run an fzf pipeline enriched with data from beads.

This works great for me personally but the part that actually pulls data out of the agent sessions is built on heuristics, and I didn't even attempt to get notifications out of it, I just side channel those out using peon-ping[1]

[0]: https://github.com/yendo-eng/remuda [1]: https://github.com/PeonPing/peon-ping

Re: Herdr is joining Y Combinator. The runtime stays open

#130

Can anyone tell me how is this different than tmux?

Mostly it’s the agents view, it’ll show the status of and let you quickly jump to all the agents you have running in any pane/tab.

It also has a default config that’s much easier to use than tmux, letting you use the mouse or simpler (IMO) keyboard shortcuts

Built in worktrees are nice too.

Post reply on HN