You've obviously written this because screen wasn't doing the right thing, but your readme only explains that it's a "young project, not a drop-in GNU screen replacement". What are its advantages over screen or tmux?
Fair. Adding a section for this now.<p>screen actually works the same way architecturally: it parses all output through its own built-in terminal emulator and redraws from that state on reattach. But that emulator is decades old and lags far behind what modern programs emit. Whatever it doesn't understand gets dropped or mangled on redraw. boo swaps that layer for libghostty-vt, Ghostty's VT core, so the saved state matches what your terminal would actually display, and terminal queries get answered while detached so TUIs don't hang unattended.<p>tmux is great, it was just never the model I wanted. I really liked screen's simplicity, sessions and a prefix key and nothing else to learn, and boo keeps exactly that.
Been using zmx for a few months and love it: <a href="https://github.com/neurosnap/zmx/" rel="nofollow">https://github.com/neurosnap/zmx/</a><p>Very similar, based on libghostty
Really dig the minimal approach here. Swapping the backend to libghostty is exactly the kind of clean architecture we need. Going to test drive this today.
I think Cmux is the incumbent in the "screen-style terminal multiplexer built on libghostty" - any key differentiators here? <a href="https://cmux.com/">https://cmux.com/</a>
Installed using the curl-to-bash on Sequoia and I’m getting “error: ReadOnlyFileSystem” on ‘boo new’. Can’t see any open issues on gh and nothing in the readme.<p>Definitely interested in something like this - love ghostty and I’ve been finding Zellij a bit crashy recently (plus I don’t really need tabs).
this looks nice! i've been using herdr the last couple of weeks as a terminal multiplexer for agents, which works amazingly well.