boo
A GNU screen style terminal multiplexer with Ghostty-accurate redraws and headless automation.
boo is a focused, well-executed multiplexer that nails the niche of screen-style session management with modern terminal accuracy. If you need persistent sessions that survive disconnects and want scriptable automation, it's a clean choice. But it's not a tmux replacement—no panes or plugins—so teams relying on those features should stick with tmux.
Verified 1d ago · liveness 67/100 · cite: rightaichoice.com/tools/boo
- Developers needing persistent terminal sessions that survive disconnects
- CI/CD pipelines running interactive commands requiring precise terminal state
- AI agents or scripts that need to read, send, and wait in headless terminals
- Users migrating from GNU screen seeking more accurate redraws
- Users needing tmux-style window splitting and panes
- Teams requiring advanced session sharing or pair programming
- Users reliant on a mature plugin ecosystem
We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.
- Honest verdict, not marketing
- Real pros & cons from real users
- Attributed quotes with receipts
3 free scans · no card needed
Skip boo if you need tmux-style panes, a plugin ecosystem, or advanced session sharing with multiple users—boo focuses on single-session detachment and automation.
boo is free and open-source, costing you nothing but setup time. Compared to commercial multiplexers or managed services, it's a no-brainer for cost-conscious developers and small teams. You only pay in learning curve and DIY support.
In short
boo — A GNU screen style terminal multiplexer with Ghostty-accurate redraws and headless automation. Best for Developers needing persistent terminal sessions that survive disconnects, CI/CD pipelines running interactive commands requiring precise terminal state, AI agents or scripts that need to read, send, and wait in headless terminals. Free to use.
What people actually say about boo — is it worth it?
We ran a structured research pass across product reviews, community discussions, and post-purchase forum threads to surface the patterns vendors won't publish themselves. Below: the recurring strengths, the hidden costs people mention most, and the cohort that consistently regrets adopting this tool.
93 mentions across 7 sources (Hacker News, YouTube, Product Hunt, App Store, Bluesky, Stack Overflow, Lemmy) · researched Jun 18, 2026.
- +Accurate screen state awareness via libghostty for reliable reattach.
- +Simple screen-like model without tmux complexity.
- +Session persistence across disconnects works well.
- +Developer is responsive and fixes bugs quickly.
- +Open source and MIT licensed, inviting customization.
- −Installation error on macOS Sequoia (ReadOnlyFileSystem).
- −Very early stage with limited community and docs.
- −No official Windows or Linux binary packages.
- −Name confusion with dating app and other products.
- −Small user base means fewer bug reports and plugins.
- • None; the tool is free and open source.
Viability Score
How well maintained and how widely used is boo? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this
Last calculated: August 2026
How we score →Key Features
- Session detach/reattach with Ctrl-A d
- Full-screen session manager (boo ui)
- Faithful redraws using libghostty terminal state
- SGR styles, cursor, and scrollback preservation
- Supports window title and terminal modes
- Headless automation: send, peek, wait
- JSON output for ls and peek
- Exit codes: 0 success, 1 error, 2 usage, 3 no session, 4 timeout
- Literal text sending with no escape processing
- Wait for text or idle with timeout
- Binary-safe stdin mode
- Session naming defaults to current directory
- Kill all sessions with boo kill --all
- Pre-built binaries for Linux and macOS
- Written in Zig for performance
About boo
boo is a free, open-source terminal multiplexer that revives GNU Screen's session management with modern terminal emulation. Built on libghostty-vt and written in Zig, it parses every session's output through Ghostty's terminal core, ensuring faithful redraws of styles, cursor, scrollback, and terminal modes. Designed for developers, sysadmins, and AI agents, boo provides persistent sessions that survive disconnects and a full suite of headless automation commands. Sessions detach with Ctrl-A d and reattach with boo attach. A full-screen session manager (boo ui) lists sessions in a sidebar. boo swaps GNU Screen's outdated emulator for Ghostty's accurate VT parser, ensuring modern TUI compatibility. Key automation primitives include send (literal text input with no escape processing), peek (rendered screen output with --json support), and wait (block until text or idle with timeout). Output is machine-readable via --json flags, and exit codes convey specific error conditions (0 success, 1 error, 2 usage, 3 no session, 4 timeout). boo is not a tmux competitor—no panes, no plugins—but excels for users who need detached session management and scriptable interactive programs. It is free, open-source, and available as pre-built binaries for Linux and macOS.
Behind the Verdict
boo is a refreshing take on terminal multiplexing, built specifically to address the limitations of GNU screen's aging terminal emulation. By leveraging libghostty-vt, it gives you the exact screen state as a human would see, which is a game-changer for automation. The headless primitives (send, peek, wait) are elegantly designed for scripting and AI agent integration. It's a perfect fit for developers who live in SSH sessions and need to pick up where they left off, or for CI pipelines that need to drive interactive programs. The lack of panes and plugins is intentional—boo is not trying to be tmux. For users who need multi-window layouts or rich plugin ecosystems, this will be a dealbreaker. However, for its target audience—minimalists, remote workers, and automation enthusiasts—boo delivers exceptional value with zero cost. The project is early-stage, so you'll need to tolerate thin documentation and occasional rough edges, but the core is solid and the philosophy is clear.
Researching boo? Get your full AI stack in 60 seconds.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Real-world workflow fit
Concrete scenarios for the personas boo actually fits — and what changes day-one when you adopt it.
SSH into a server and start a long-running build process
Outcome: Detach with Ctrl-A d, log off, and reattach later with boo attach to see the exact output, preserving cursor and scrollback.
Automate an interactive install script in a headless pipeline
Outcome: Use boo new, send, wait, peek to drive the script, capture JSON state, and clean up with boo kill.
Build an agent that reads and interacts with a terminal
Outcome: Use boo's headless primitives to send commands, wait for output, and peek at screen state without a TTY.
Use Cases
- Persist terminal sessions across network disconnects while working remotely
- Reattach to a session and see exactly the same screen state as when detached
- Automate terminal monitoring by parsing accurate screen content
- Build AI agents that can read and interact with terminal output predictably
Limitations
- boo is a terminal multiplexer built on libghostty that provides faithful redraws, session management, and headless automation.
- It supports JSON output and exit codes for scripting, but is an early-stage open-source project with limited documentation.
- Pre-built binaries are available for Linux and macOS.
as of 2026-08-14
Verification history
We have re-verified boo 10 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
Showing the 6 most recent of 10 verification passes.
Free to cite with attribution — this page re-verifies continuously.
12-month cost
Project the real annual outlay, including the implied monthly cost when only an annual tier is published.
Vendor list price only. Add-on usage, seat overages, and contract minimums are surfaced under Hidden costs & gotchas.
Plans compared
For each published boo tier: who it actually fits, and what it adds vs. the previous tier. Cross-reference the cost calculator above for projected annual outlay.
Free
$0/mo
Ideal for
Solo developers, sysadmins, and automation enthusiasts who need persistent sessions and scripting without cost.
What this tier adds
Starting tier: all features included at $0/mo, no paid upgrades planned.
Where the pricing makes sense
The company stage and team size where boo's pricing actually pencils out — and where peers do it cheaper.
boo is free and open-source, costing you nothing but setup time. Compared to commercial multiplexers or managed services, it's a no-brainer for cost-conscious developers and small teams. You only pay in learning curve and DIY support.
Setup time & first value
How long it actually takes to get something useful out of boo — broken out by persona, not the marketing-page minute.
For most users, install via curl and boo new gets you a working session in under a minute. Automation users need about 10 minutes to learn send/wait/peek. Full adoption with scripting may take an hour.
Switching to or from boo
How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.
- →From GNU screen: start boo with boo new, map your muscle memory—key bindings are similar (Ctrl-A d). You'll get accurate redraws.
- →From tmux: if you only need detached sessions, make boo new and boo attach your daily workflow. No panes to port over.
- ↗To tmux: run tmux new-session, recreate your sessions manually. No direct migration command exists.
Resources & Guides
Tutorials & Learning
Official links
Featured Head-to-Head Comparisons
Boo vs Temporal Ai
Temporal AI and boo solve entirely different problems. Temporal is a heavy-duty durable execution platform for building fault-tolerant AI agents and multi-step workflows – ideal for teams that need crash resilience and full visibility. boo is a lightweight terminal multiplexer for managing persistent shell sessions, best for developers and scripts that need reliable terminal automation without the overhead of tmux or screen. Choose Temporal for robust orchestration, boo for session management.
Boo vs Audioeye
boo and AudioEye serve completely different needs. If you're a developer needing persistent terminal sessions or headless automation, boo is free and purpose-built. If you're an enterprise facing ADA/WCAG compliance deadlines or legal risk, AudioEye provides automated scanning, human audits, and VPAT documentation, but at a cost. Choose based on your domain: terminal vs. accessibility.
Boo vs Spider Cloud
Spider Cloud and boo serve entirely different needs: Spider Cloud is a web scraping API for AI data pipelines, while boo is a terminal multiplexer. There is no direct competition. Choose Spider Cloud if you need structured web data for agents or RAG; choose boo for persistent terminal sessions. They are complementary, not substitutes.
Popular in Code & Development
Frequently Asked Questions
Categories
Best-of guides
Topics
Used boo? Help shape our editorial sentiment research.