Honest writing about what we're making, what we've shipped, what's broken, and what we're learning while building a gesture-based terminal multiplexer for the AI-agent era.
A full audit, accurate as of May 2026 — every shipped feature, every paused feature, every abandoned feature.
Deep dives: where gmux came from, how each implementation evolved, where it sits in the ecosystem.
The clean product overview. What it is, the three layers it ships in, the gesture vocabulary, the voice routing, the phone remote, and how it compares to Multica, qalcode2, Warp and DeepSeek-TUI.
Read overview Research · 02From the April assembled prototype to the abandoned transparent overlay (killed by Wayland) to the Tauri app that owns the terminal. A technical review of all six implementations, with the architectural decisions logged honestly.
Read implementations Research · 03The annoying-to-solve problem of ten parallel agents in tmux. The state-detection bug fix. The Wayland trap. The port collision with aria-phone. The installer freeze decision. The honest story of what got built, broke, and got rebuilt.
Read the devlog Research · 04Three layers of AI tooling: orchestration (Multica), execution (qalcode2, Hermes, Claude Code), interaction (gmux). Most tools cover the middle; almost nothing covers the third. This is where the moat is.
Read the positioningShorter pieces — one idea each. The pitch, the architecture, the gesture vocabulary, the phone, the memory layer, and the roadmap.