The House That Stability Built
To understand the tension within tmux, you have to understand its origin. Created in 2007 by Nicholas Marriott, tmux was born out of frustration with the existing tool, GNU Screen. In an early interview, Marriott described Screen as having 'a lot of baggage',
citing its poor documentation, strange configuration, and an unintuitive interface. His goal wasn't just to build an alternative, but to create something with a clean, readable, and extendable codebase. This ethos of deliberate, clean design is baked into the DNA of tmux. For most of its life, the project has operated under a 'founder-leader' model, where the original creator sets the vision and holds the final say. This isn't a democracy; it's a project guided by a specific philosophy of what a terminal multiplexer should—and shouldn't—be.
A Philosophy of Careful Evolution
The core promise of tmux was never about chasing trends. It was about stability and a client-server architecture that separates the user's view from the running sessions. This means you can detach from a session, lose your internet connection, and reconnect later to find all your programs running exactly as you left them. Marriott was clear that tmux shouldn't add features just because Screen had them; every addition had to align with the project's core principles. This resulted in a tool that is famously scriptable, reliable, and consistent. For more than a decade, its user base of software developers and system administrators appreciated tmux for what it was: a powerful, predictable tool that did its job without fanfare. Its direction was steady, guided by a single maintainer focused on quality over quantity.
An Unexpected Second Act
Then, around 2025, something changed. The rise of powerful AI coding agents like Claude Code created a new problem for developers. These agents often run as long-lived processes that need to be monitored and managed, sometimes in parallel. Developers quickly realized that the perfect environment for orchestrating these AI teams already existed on their machines. Almost by accident, tmux became the de facto runtime for AI agent development. Its ability to maintain persistent sessions, split a terminal into multiple panes, and allow users to detach and reattach at will was exactly what the new workflow demanded. A tool built for human developers in 2007 turned out to be the ideal workplace for AI agents nearly two decades later.
The Inevitable Philosophical Divide
This brings us to the 'disagreement' over direction. It isn't a public feud or a dramatic schism. Instead, it's a fundamental tension between the project's original philosophy and the demands of its explosive new use case. On one side is the vision that made tmux successful: a stable, general-purpose tool that evolves slowly and deliberately. On the other side is the pull of a massive new audience using tmux in ways its creator never explicitly intended. Should the project now cater to these AI developers? Should it add features specifically for agent orchestration? Doing so could mean faster development and new features, but it could also introduce the kind of complexity and 'baggage' that Marriott sought to escape in the first place. This is the classic governance challenge for a successful open-source project: when the person who 'does the work' has a clear vision, how much should that vision bend to the will of a new, vocal user base? It’s a conflict between maintaining a tool's soul and embracing its unexpected future.













