So I stopped using Ghostty...

TL;DR

Theo switched from Ghostty to Zellij-like terminal Zellij alternative Zedmux — wait, to **Zellij** — to **Semox** because parallel agentic coding broke his tmux-based workflow.

Key Points

• 1.Why he left Ghostty: Not because Ghostty is bad — it's fast, open-source, and well-maintained — but because his parallel agentic coding workflow outgrew what any terminal + tmux combo could organize cleanly.
• 2.What Semox is: A terminal built on libghostty (the same core library powering Ghostty), made by the two-person Manoflow team. Theo disclosed he invested in Manoflow before knowing they were building Semox.
• 3.The key feature he loves: A sidebar of named project workspaces (e.g., "T3 Code," "Sandbox," "Benchmarks"), each with its own split panes and tabs — mapping projects to a hierarchy instead of flat tmux windows.
• 4.Claude Code integration: Semox detects Claude Code terminals and shows status notifications when Claude needs input, letting Theo work in another pane and get pinged when attention is needed.
• 5.What bugs him about Semox: A doubled status bar glitch in Zsh, and a built-in browser (a janky Safari WebView with no extensions or saved cookies) that hijacked terminal links — he immediately turned that off.
• 6.His vision for what's next: Inspired by the Niri "paper window manager" (infinite horizontal/vertical scrolling panes that don't shrink each other), he wants Semox to become a single app combining scrollable terminals, a real Chrome instance with your actual profile, and IDE panes like VS Code or T3 Code.
• 7.Why MacOS Spaces don't solve this: Spaces isolate where they shouldn't and bleed through where they should isolate — slow animations (up to half a second), broken Command-Tab behavior, and no way to disable the sluggish transitions make them unusable for heavy parallel dev work.