Alternatives
Products that do what cmux - Ghostty-based terminal with vertical tabs and notifications does
I run a lot of Claude Code and Codex sessions in parallel. I was using Ghostty with a bunch of split panes, and relying on native macOS notifications to know when an agent needed me. But Claude Code's notification body is always just "Claude is waiting for your input" with no context, and with enough tabs open, I couldn't even read the titles anymore. I tried a few coding orchestrators but most of them were Electron/Tauri apps and the performance bugged me. I also just prefer the terminal since GUI orchestrators lock you into their workflow. So I built cmux as a native macOS app in…
- 1
- 2CC
HN, I'm stoked to share this product I've been working on non-stop for the past few weeks. It's an immersive GUI experience for working with many coding agents in parallel. The UX should be familiar to Claude Code users, but we took advantage of the GUI nature to add in a bunch more. cmux is early but certainly usable—almost all of our internal cmux development rolls through cmux itself. Please let me know your thoughts and feedback!
Oct 2025 · github.com
- 3
- 4
- 5
- 6RA
Author here. RMUX started from a frustration: I've used tmux for years and got tired of scraping output with grep and sleeps to automate anything. So I rebuilt the multiplexer from scratch in Rust, with a programmable layer on top. Two surfaces: a tmux-compatible CLI (~90 commands, your keybindings just work), and a typed async Rust SDK on the same daemon — stable pane IDs, structured snapshots, locator-style waits. The idea is Playwright-style automation, but for terminals. Native on Linux, macOS, Windows (real ConPTY, no WSL). Demos and docs at rmux.io. Happy to answer questions about the…
May 2026 · github.com
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18CC
Hello everyone. Claudraband wraps a Claude Code TUI in a controlled terminal to enable extended workflows. It uses tmux for visible controlled sessions or xterm.js for headless sessions (a little slower), but everything is mediated by an actual Claude Code TUI. One example of a workflow I use now is having my current Claude Code interrogate older sessions for certain decisions it made: https://github.com/halfwhey/claudraband?tab=readme-ov-file#s... This project provides: - Resumable non-interactive workflows. Essentially `claude -p` with session support: `cband continue…
Apr 2026 · github.com
- 19
- 20DC
After a year of producing all my code through Claude Code, I was growing frustrated with losing Terminal tabs and not noticing when sessions are ready to continue. I looked around at all the terminal managers people have been building for this type of workflow and couldn't find anything that worked for me. Cmux came close but was too buggy in the area I cared the most about: knowing when my sessions are ready for input. I also felt like the sidebar was too cluttered and hard to parse visually. So, I made my own Claude-first terminal manager and optimized it for the habits I've developed over…
Apr 2026 · github.com
- 21IB
Hi HN, I built this because I got tired of the Claude Code CLI hiding details from me. Recent updates have replaced critical output with summaries like "Read 3 files" or "Edited 2 files". To see what actually happened, I was forced to use `--verbose`, which floods the terminal with unreadable JSON and system prompts. I wanted a middle ground: *Full observability without the noise.* `claude-devtools` is a local Electron app that tails the session logs in `~/.claude/` to reconstruct the execution trace in real-time. *Unlike wrappers, it solves the visibility gap in your native…
Feb 2026 · github.com
- 22
- 23OS
2024 · github.com
- 24
Ranked by how close each launch is in meaning, then by votes. Refine with a description →