
A screen-style terminal multiplexer with Ghostty-accurate redraws and headless automation.
By Tanmay Verma, Founder · Last verified 20 Jun 2026
In short
boo — A 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 that require precise terminal state, AI agents or scripts that need to read, send, and wait in headless terminals. Free to use.
Affiliate disclosure: We earn a commission when you use our links. Editorial picks are independent. How we choose.
See what real users actually say. We scan live discussions, reviews and complaints across the web and hand you an honest verdict — in under a minute.
3 free scans · no card needed · downloadable report
boo is a fresh take on screen-style multiplexing with an accurate emulation core that solves reattach flakiness. Its automation API is a standout for CI and AI-driven terminal tasks. However, it's early-stage and lacks tmux's ecosystem; adopt for simple session needs or headless automation, not complex layouts.
Last verified: June 2026
boo occupies a narrow but valuable niche: developers and sysadmins who rely on GNU screen but are frustrated by its outdated terminal emulation and flaky redraws. By leveraging Ghostty's libghostty-vt, boo ensures that when you reattach to a session, you see exactly what you left—styles, cursor, scrollback, and all. This is a genuine improvement over screen and even tmux in some edge cases. The automation API is a standout feature: commands like `send`, `peek`, `wait`, and `--json` output make it easy to script interactive terminal workflows or build AI agents that read and write terminal state without a TTY. This could be a game-changer for CI/CD pipelines that need to interact with tools like `make`, `npm`, or `ssh` in a headless environment. That said, boo is still very early. Version numbers aren't advertised, documentation is limited to the README, and community support is nascent. It deliberately skips features like tmux-style pane splitting and session sharing, which limits its appeal for teams or complex layouts. Windows support is absent, and there's no plugin ecosystem. For now, boo is best suited for single-session-per-task workflows—think remote development over SSH, automated testing, or monitoring daemons. If you need robust session management with automation-first design, boo is worth a look. If you need split panes, mature tooling, or cross-platform support, stick with tmux or screen.
Skip boo if Skip boo if you need tmux-style window splitting, pane management, or cross-platform support, as it focuses on single-session workflows and only runs on Linux and macOS.
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).
How likely is boo to still be operational in 12 months? Based on 4 signals — momentum (how recently it shipped), wrapper dependency, revenue model, and web presence.
Last calculated: June 2026
How we score →boo is a terminal multiplexer that reimagines GNU screen's model with modern terminal emulation from Ghostty's libghostty-vt core, written in Zig. It provides persistent sessions that survive disconnects, faithful screen redraws including styles, cursor, and scrollback, and agent-friendly automation primitives. Ideal for developers, sysadmins, and AI/scripting workflows who need a reliable session manager with headless operation. Key features include session detach/reattach, a full-screen session manager (`boo ui`), and automation commands like `send`, `peek`, `wait` with JSON output and exit codes. Unlike tmux, boo keeps screen's minimalist prefix-key model but replaces its outdated emulator with Ghostty's accurate VT parser, ensuring modern TUI compatibility.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Concrete scenarios for the personas boo actually fits — and what changes day-one when you adopt it.
You run `boo new work` to create a session, then detach with Ctrl-A d. After a network disconnect, you SSH back and run `boo attach work` to resume exactly where you left off.
Outcome: No lost work, full terminal state restored including cursor position and styled output.
You create a headless session with `boo new build -d -- make`, send commands with `boo send build --text 'make' --enter`, wait for idle with `boo wait build --idle`, and read the output with `boo peek build --scrollback`.
Outcome: Reproducible, scriptable interaction with native terminal programs, all without a TTY.
Your agent spawns a session, sends a series of commands, parses JSON output from `boo peek`, and makes decisions based on exit codes and screen content.
Outcome: Accurate, deterministic terminal interaction that an AI can interpret reliably.
boo is currently in early development with limited documentation and community support. It lacks advanced multiplexer features like window splitting, pane management, or session sharing.
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.
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 (MIT), making it cost-effective for any budget. It fits individuals and teams alike, with no pricing tiers.
How long it actually takes to get something useful out of boo — broken out by persona, not the marketing-page minute.
Install boo on Linux or macOS via curl: `curl -fsSL https://raw.githubusercontent.com/coder/boo/main/install.sh | sh`. Takes less than a minute. For first-time users, creating and attaching to a session is immediate after installation.
How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.
Pricing, brand, ownership, or deprecation changes worth knowing before you commit. Most-recent first.
Boo vs Spider Cloud
Spider Cloud and boo serve completely different domains: Spider Cloud is a web scraping API for AI agents, while boo is a terminal multiplexer. Choose Spider Cloud if you need to extract web data at scale for LLMs or RAG pipelines. Choose boo if you need persistent terminal sessions with accurate redraws or headless terminal automation. They are not direct competitors.
Boo vs Temporal Ai
Temporal AI and boo are not direct competitors: Temporal is a durable execution engine for orchestrating complex AI/backend workflows with automatic resilience, while boo is a terminal multiplexer for persistent shell sessions. Choose Temporal if you need to build fault-tolerant AI agents or manage multi-step distributed processes; pick boo if you want a reliable, headless session manager for terminal automation and scripting.
Boo vs Audioeye
boo and AudioEye serve completely different needs: boo is a free terminal multiplexer for developers needing persistent sessions and headless automation, while AudioEye is a paid enterprise accessibility platform for ADA/WCAG compliance. Choose boo if you're a developer or sysadmin; choose AudioEye if you're an organization facing legal accessibility requirements.
Used boo? Help shape our editorial sentiment research.