For me, herdr's benefits over terminal splits are:
1. Surfacing agents which are ready for further input
2. Letting you jump quickly to said agents
3. SSH session persistence, as I work on a beefy devbox at work. tmux also offers this.
I often need to juggle several streams of work at $job in parallel - such are the expectations.
Like you though, I'd much prefer to use my terminal directly with the indirection of an additional multiplexer like herdr or tmux - lower latency, easier scrollback & copying.
Session persistence can be solved by zmx [1].
Points 1 and 2 however are concerned with tracking the state of and navigating to parallel agents. I'm thinking about creating a TUI or SwiftUI app to handle those points in the way I like, but the challenge of integrating such an app with zmx and kitty to jump to the right panes both locally and over a devbox is a little daunting. Plus, I've found my devbox doesn't play too well with `ControlMaster auto` SSH config suggested by the zmx docs.
[1] https://github.com/neurosnap/zmx
1. Surfacing agents which are ready for further input
2. Letting you jump quickly to said agents
3. SSH session persistence, as I work on a beefy devbox at work. tmux also offers this.
I often need to juggle several streams of work at $job in parallel - such are the expectations.
Like you though, I'd much prefer to use my terminal directly with the indirection of an additional multiplexer like herdr or tmux - lower latency, easier scrollback & copying.
Session persistence can be solved by zmx [1].
Points 1 and 2 however are concerned with tracking the state of and navigating to parallel agents. I'm thinking about creating a TUI or SwiftUI app to handle those points in the way I like, but the challenge of integrating such an app with zmx and kitty to jump to the right panes both locally and over a devbox is a little daunting. Plus, I've found my devbox doesn't play too well with `ControlMaster auto` SSH config suggested by the zmx docs.
[1] https://github.com/neurosnap/zmx