1) are terminal based (not gui apps that you need to install)

2) Can be run by mosh/ssh

3) Track agent sessions automatically

4) Have built-in git worktree management

5) Show agents connections over different machines (the new feature mentioned in the blog post)?

There is also netbird, netmaker, zerotier and several others.

I got PRs that either never worked or even broke stuff

https://blog.codepipes.com/llms/your-pr-was-rejected.html

1) Built-in sub agents assume you use a single AI agent. Some people use multiple, so they need separate terminals/processes by definition. Even if you use the same agent sometimes you have different security boundaries. Think also the needs for a consultant working with many customers at once.

2)Multiple-open terminals. When that number passes 5-7 for me, then yes I don't like clicking on each one of those manually to see where my attention is needed. Herdr (and similar tools) show exactly what is working and what stalled.

3) No I use herdr locally mostly right now. But since it is just ssh I like the fact that you can run it from anywhere. I haven't done it yet, but I imagine you could open a herdr session from a steamdeck to a remote server to debug somthing

Another thing I like on herdr is easy work trees. Sure you can do it manually with git commands, or ask the agent itself to use a new worktree, but just having workrees with a single click and a visual tree/children hierarchy was the killer feature for making me look at herdr at the first place.

Yes technically you can do the same thing with just many terminals and custom scripts. But it is the same question of why Dropbox sells when you could do the same thing with cvs/ftp :-)

Why? Because it has more/better features. Or you mean something else?

Specifically against cmux, it is not Macosonly. So you can run it directly on a linux server and then ssh/mosh from anywhere.

I have seen moshi.app but haven't tested it yet.

They will not handle any architectural problems (i.e. this method is correct but doesn't belong on this package, or this method is called isX - but has side effects).

And I am pretty sure that none of them do what I am saying with the tests. i.e. run tests without the associated code change and see them fail. I am also pretty certain that none of them will understand problems with breaking backward compatibility (i.e., a fix that is correct that breaks the setup of all existing users).

In other words, it is possible today to create a PR that passes all checks, all security scans, all analysis tools, all test suite while still being wrong due to architecture, backwards compatibilty, wrong scope etc. So even before and even after LLMs a human is needed there.

PRs might become unhelpful as you say if in the future one of the two things we happen

1) LLMs have unlimited context so you can pass all source code plus all architectural designs them 2) We have a super smart analysis tool that is one level above what we have today (including llms)

We are not there yet.

manual PR reviews can catch things that llms currently miss. Examples are duplicated code, lack of unit tests or introducing security issues. None of these really break the build. So just requiring "do not break the build" is a very low barrier.

Tests also are useless unless you have a smart system that runs the new test WITHOUT the changes and see it break. Most teams I see today have the LLM write a test along with the change, without a guarantee that the tests actually guard the feature.

For me the killer feature is the git worktree management.

But in essence it is tmux on steroid (Specifically for agents)

First iroh was marketed as "solves communication behind NAT". Then we went to application level NAT busting vs node level NAT busting. Then we went to distributed vs client-server, then we went to stable IPs for non-server devices (your original comment). Now we moved to "true peer to peer" and "public keys".

This just tells me that the marketing site doesn't explain what Iroh actually does.

The fact that so many other people (apart from me) asked about the connection to Tailscale is also interesting.

For this simple scenario (just exposing your laptop to a public IP) there are already a gazillion alternatives (e.g. ngrok)