Why would I want the terminal coding agents inside of a GUI app? The idea is terrible.
The first point in the explanations below makes no sense, claiming my agents will "keep working" if I close my notebook's lid or disconnect the network.
Some people like to run their agents on different headless servers. Herdr is cool because you can connect via ssh and use herdr on that machine from anywhere. When you close the client or disconnect, herdr is still running on the host.
> Why would I want the terminal coding agents inside of a GUI app?
Because they get difficult to manage with enough of them and multiple projects. The GUI helps them stay organized, especially with multiple harnesses. Herdr is a minimal GUI, and works like a simple tmux, which is why I like it.
It looks like crap.
Why would I want the terminal coding agents inside of a GUI app? The idea is terrible.
The first point in the explanations below makes no sense, claiming my agents will "keep working" if I close my notebook's lid or disconnect the network.
This is obviously not the case.
Some people like to run their agents on different headless servers. Herdr is cool because you can connect via ssh and use herdr on that machine from anywhere. When you close the client or disconnect, herdr is still running on the host.
> Why would I want the terminal coding agents inside of a GUI app?
Because they get difficult to manage with enough of them and multiple projects. The GUI helps them stay organized, especially with multiple harnesses. Herdr is a minimal GUI, and works like a simple tmux, which is why I like it.
My mental model (and I don't really use it) is it's agent-aware tmux.