It seems like the main selling point is going to be performance over tmux(or really any multiplexer) with the anticipation of giant multiplexer sessions resulting from increased AI agent usage(which is talked about in this video https://www.youtube.com/watch?v=T5gV6anSt-4).
I'm fairly new to using multiplexers and not a hardcore user as I'm mostly getting my feet wet with herdr at the moment. For the hardcore users, is performance really a bottleneck? How big are your sessions that you have rendering issues?
Regardless, whenever Mitchell talks, I'm interested so I'm signed up for the release notification and will definitely check it out!
With the recent videos, I think there are multiple selling points.
* General performance.
* Run the server and client everywhere. There are already multiple libghostty clients for mobile. Native terminal support on mobile is great, especially for coding agents.
* Native sessions. The lack of sessions in terminals is part of the reason why some people went with tmux in the first place.
* Multiplexer performance isn’t noticeable until you start running multiple sessions with multiple agents. Sometimes half of my RAM ends up being allocated to Ghostty/Alacritty + tmux.
* As for rendering, performance is one thing. But the multiplexer tax is really, really annoying. For example, some features are available in Ghostty but not tmux, and vice versa. It’s the little things that pile up.
Another point is that, for some reason, multiplexers and terminals often diverge in terms of feature implementation. Probably because one traditionally focuses more on remote workflows, while the other focuses on local workflows. With AI, though, it makes a lot more sense to have both. Running long-lived sessions with agents is becoming normal, so the line between those use cases is getting thinner. That’s probably why they’re focusing on this approach.
It seems like the main selling point is going to be performance over tmux(or really any multiplexer) with the anticipation of giant multiplexer sessions resulting from increased AI agent usage(which is talked about in this video https://www.youtube.com/watch?v=T5gV6anSt-4).
I'm fairly new to using multiplexers and not a hardcore user as I'm mostly getting my feet wet with herdr at the moment. For the hardcore users, is performance really a bottleneck? How big are your sessions that you have rendering issues?
Regardless, whenever Mitchell talks, I'm interested so I'm signed up for the release notification and will definitely check it out!
With the recent videos, I think there are multiple selling points.
* General performance. * Run the server and client everywhere. There are already multiple libghostty clients for mobile. Native terminal support on mobile is great, especially for coding agents. * Native sessions. The lack of sessions in terminals is part of the reason why some people went with tmux in the first place. * Multiplexer performance isn’t noticeable until you start running multiple sessions with multiple agents. Sometimes half of my RAM ends up being allocated to Ghostty/Alacritty + tmux. * As for rendering, performance is one thing. But the multiplexer tax is really, really annoying. For example, some features are available in Ghostty but not tmux, and vice versa. It’s the little things that pile up.
Another point is that, for some reason, multiplexers and terminals often diverge in terms of feature implementation. Probably because one traditionally focuses more on remote workflows, while the other focuses on local workflows. With AI, though, it makes a lot more sense to have both. Running long-lived sessions with agents is becoming normal, so the line between those use cases is getting thinner. That’s probably why they’re focusing on this approach.
Website is here, with a link for the waitlist: https://www.superlogical.com/