TL;DR
Get networking and server gear delivered free — and shop member deals
- Fast, free delivery on millions of items
- Access to Prime Big Deal Days deals on October 6–7
- Prime Video, Amazon Music and more included
A post titled “Make Tmux the OS” proposes borrowing tmux’s persistent, detachable sessions and task-oriented organization for a desktop interface designed for everyday users. It is a design thought experiment, not a released operating system or product; the author argues that current desktops handle changing screens, varied window habits and browser-based work poorly.
A software writer has proposed a desktop interface built around tmux-style sessions—persistent, detachable workspaces organized by task—in a post called “Make Tmux the OS.” The idea is a design thought experiment, not an announced operating system: its author says the challenge is to make the terminal tool’s workflow accessible to ordinary desktop users.
The author describes tmux as useful because its sessions can persist, be detached and resumed, and organize work around tasks. The proposed change is not simply to put a terminal on the desktop; it is to adapt those properties into a broader desktop interaction model. The source does not present a working prototype, implementation plan or claim that tmux itself should replace existing operating systems.
The post grounds the idea in everyday problems with changing display setups. The author moves between a laptop screen and an external monitor or monitors several times a day. On a multi-monitor desk, one display may hold peripheral material such as chat or a to-do list while another is used for focused work. Disconnecting the laptop then forces windows to be rearranged manually, the author says.
It also argues that desktop software should better accommodate different window-management habits: people who maximize one application, keep a main window alongside smaller reference windows, or deliberately arrange many windows. The author distinguishes public work from private windows that may contain information unsuitable for a passerby or presentation audience. Browser tabs are another focus: the writer says tabs often support work spanning several applications, while operating systems generally treat the browser as just one application among many.
A Desktop Built Around Ongoing Work
The proposal matters as a design argument about what a desktop should organize: individual application windows, or the work a person is trying to complete across those applications. A session-based approach could, in principle, preserve a work setup as people move between a docked desk and a laptop display, rather than making them rebuild it each time. That is the author’s intended direction, not a demonstrated result.
The question also reaches beyond developers who already use terminal tools. The writer explicitly wants the persistence and task focus of tmux without requiring users to operate a command-line interface. If that translation were made successfully, it could offer an alternative to desktops centered mainly on overlapping windows, application switching and manually managed browser tabs. The source does not establish how such a system would handle accessibility, privacy controls, or the many different ways people organize work.
As an affiliate, we earn on qualifying purchases.
The Problems Behind the Proposal
The post was prompted by a talk from Scott Jenson, titled “Are we really going to use the same Desktop UX forever?” The author agrees that desktop interaction deserves fresh thinking, while qualifying the talk’s argument: Apple and Microsoft may be conservative, the writer says, but are not necessarily inactive. The central concern is that familiar desktop conventions can preserve tradeoffs shaped by older hardware even as people’s devices and work patterns change.
To support the point that these concerns are not new, the author refers to research on multi-monitor use. They cite a 2001 finding that people commonly use one screen for focal work and another for peripheral information, and a 2004 study describing distinct window-management styles and a separation between public and private windows. These references are presented by the author as background for the proposal; the post does not supply enough detail here to independently assess the studies’ methods or how broadly their findings apply today.
The post also challenges the idea that all work is neatly represented by files and applications. Notes, messages and workplace chats may remain inside their services, while browser tabs can serve several tasks. The author describes these as cross-application work relationships that a conventional desktop may not represent well. They acknowledge that browser tabs can serve more than one task, a complication their concept has not resolved.
“The thing I want is ‘tmux is the OS’, but I want tmux where a normal person could use it.”
— The post’s author
task management software for desktop
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
From Concept to Usable Interface
The post presents a personal design exercise; it does not announce software, a development team, a release date or user testing. It remains unclear what the proposed interface would look like, how users would create and switch between sessions, or how it would support people who prefer maximized windows and conventional application switching.
Other unresolved issues include how a workspace should respond when displays are connected or removed, how public and private windows would be separated, and whether browser tabs could belong to several tasks at once. The author flags that last question as a point where their thinking departs from the research they cite. No evidence in the supplied source shows that the concept solves these problems or that the cited older research describes all current users.
As an affiliate, we earn on qualifying purchases.
The Idea Needs a Prototype
The immediate next step is discussion and design work, not a scheduled product launch. The author frames the post as a prompt for others to think about desktop interaction and says they are not a UI or UX designer. The source gives no announced follow-up milestone, prototype, or commitment from an operating-system maker.
For the concept to move beyond an argument, a future proposal would need to show how sessions work in a graphical interface, test whether users can understand and control them, and demonstrate what happens as screens and applications change. Until then, “Make Tmux the OS” is best read as a critique of current desktop organization and an invitation to explore a different model, not as a report of a new OS in development.
As an affiliate, we earn on qualifying purchases.
Key Questions
Is a new operating system called Make Tmux the OS being released?
No. The source is a design thought experiment. It does not announce a product, release date or working implementation.
What does the author mean by making tmux the OS?
The author wants to adapt tmux’s persistent, detachable, task-oriented sessions into a desktop interface that people could use without relying on terminal commands.
What desktop problems does the post identify?
It points to repeated rearrangement when displays change, differing preferences for window layouts, privacy concerns around visible windows, and browser tabs that support work across applications.
Is there a prototype or a confirmed development schedule?
The supplied source describes no prototype, development team or schedule. It presents the idea as a prompt for further thinking.
Source: hn
Fall Picks
fall essentials
As an affiliate, we earn on qualifying purchases.
