Show HN: Boo – Screen-style terminal multiplexer built on libghostty

48 pointsposted 5 hours ago
by kylecarbs

18 Comments

stereo

4 hours ago

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?

kylecarbs

4 hours ago

Fair. Adding a section for this now.

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.

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.

dgnemo

3 hours ago

can you share more on the tmux model vs boo?

drzaiusx11

an hour ago

Tmux is n clients to 1 server.

Screen is 1 server to 1 client.

In screen each client session is a fork of the screen server. In tmux there's one server and many client forks iirc.

gguingff

an hour ago

this is incorrect. you can have multiple clients using screen -x instead of screen -a

drzaiusx11

an hour ago

I didn't say you couldn't have multiple clients, I said clients and servers are the same process forked. Or did someone add distinct client/server support to screen finally? I know theres a lot of stuff bolted onto screen over the years but I wasn't aware they dropped forked servers for the tmux model...

kylecarbs

3 hours ago

I want boo to be a screen replacement, not a tmux replacement. tmux gives you a whole workspace: layout, scrollback, copy mode, a status bar. screen's appeal was that it did almost none of that: sessions, a prefix key, done. boo keeps that model and swaps the emulation for libghostty so reattach actually redraws correctly.

They also compose: a boo session is just a PTY running a program, so you can run tmux inside one if you want.

boltguo

an hour ago

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.

johnfn

2 hours ago

I think Cmux is the incumbent in the "screen-style terminal multiplexer built on libghostty" - any key differentiators here? https://cmux.com/

kylecarbs

2 hours ago

Cmux is a standalone terminal. Boo is a command-line similar to screen, backed by libghostty for terminal emulation.

darkteflon

3 hours ago

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.

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).

relyks

38 minutes ago

How have you been using Zellij? It's been working great for me

kylecarbs

3 hours ago

I'll take a look at this now. Thanks for reporting!

kylecarbs

3 hours ago

Just published v0.5.13 which should fix this! It seems to be a path issue. Now boo falls back to tmpdir for storing sockets.

asar

4 hours ago

this looks nice! i've been using herdr the last couple of weeks as a terminal multiplexer for agents, which works amazingly well.