TL;DR
Get the latest gadgets 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 adapting tmux’s persistent, detachable, task-oriented sessions into a desktop interface usable by people who do not work in terminals. It is a design thought exercise, not a product announcement; the author argues that today’s window systems handle changing displays, different work habits and browser-based work poorly.
A software engineer writing on matduggan.com has proposed a desktop interface built around persistent, detachable work sessions, taking inspiration from the terminal multiplexer tmux. The piece, titled “Make Tmux the OS,” is a design thought exercise, not an announcement of a finished operating system or product.
The author’s central idea is to make the useful parts of tmux—scrollable sessions, persistence and detachment—available through an interface ordinary desktop users could operate. In tmux, people can keep work running across terminal sessions and disconnect or reconnect without treating every window as a separate, temporary object. The proposal asks whether a desktop could organize activity around that kind of continuing work.
The post frames the idea as a response to several problems in existing window management. People move repeatedly between a laptop screen and external displays, yet typically have to manually rearrange windows when the display setup changes. The author also distinguishes users who maximize one window, those who keep a main window alongside smaller reference or status windows, and those who arrange many windows deliberately. The post says current systems tend to favor the first pattern.
Other issues in the essay include the separation between browser tabs and desktop applications, and the difficulty of keeping work organized across them. The author describes browser tabs as part of streams of work, rather than simply content inside an application window. They also argue that much digital information now sits inside services such as Notes, messaging apps and collaboration tools instead of in a conventional filesystem. The provided excerpt begins to address that point but does not include the full discussion.
A Desktop Organized Around Work
The proposal matters as a critique of a desktop model that still treats windows, applications and displays as the main units of organization. For people who regularly switch between docked and mobile setups, manually restoring a useful arrangement can interrupt work. A session-based interface could, in principle, make work easier to resume and carry between configurations.
It also puts a familiar tension in focus: desktop software must support different habits without forcing everyone into one layout. A persistent workspace might help someone keep related tools together, but would need to handle private material, peripheral information and shared screens carefully. The author raises those design challenges; the post does not establish that a tmux-inspired system would solve them.
As an affiliate, we earn on qualifying purchases.
The Window-Management Problem
The author connects the proposal to a talk by Scott Jenson, titled “Are we really going to use the same Desktop UX forever?” Jenson’s argument, as summarized in the post, is that established desktop makers are unlikely to drive major change and that others should think about what a future desktop could be. The author qualifies that view, saying Apple and Microsoft do try ideas but are extremely conservative.
The essay points to earlier research as evidence that some complaints are longstanding. It cites a 2001 finding by Grudin about people using a second monitor for peripheral material while keeping focal work on the primary display. It also refers to a 2004 study, “Revisiting Display Space Management: Understanding Current Practice to Inform Next-generation Design,” for the distinction between different window-management styles and between public and private windows. These references are presented by the author; the supplied material does not include the studies themselves or independently verify their findings.
The piece is explicit about its status: its author says they are not a UI/UX designer and describes the proposal as a thought exercise intended to prompt discussion. The available source excerpt names a concept called WindowScape but does not provide enough detail to explain its mechanics or assess how it would work.
“The thing I want is “tmux is the OS,” but I want tmux where a normal person could use it.”
— The author of “Make Tmux the OS”
desktop organization tools for productivity
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
A Concept, Not a Product
The source describes a proposal rather than a working system. It does not identify a developer team, software release, prototype, funding, implementation schedule or plans for testing the idea with users. Nor does the supplied excerpt explain how sessions would handle applications that do not support persistence, browser tabs used across multiple tasks, or private windows that could appear on an external display.
The claims about how common particular work habits are are also not established independently in the material provided. The author cites research from 2001 and 2004, but the excerpt does not give study methods or results in detail. The publication date of the post is not supplied, so its references to “2026” should be understood as the author’s framing, not a verified publication date.
As an affiliate, we earn on qualifying purchases.
Whether the Idea Gains a Prototype
No next release or milestone is announced in the supplied material. The immediate next step is discussion: the author presents the essay as a prompt for other people to think about desktop design. Any prototype, user research or follow-up explaining WindowScape would be needed to show how the proposed session model might handle everyday applications, changing displays and private information.
Until such details appear, “Make Tmux the OS” is best read as a design argument about organizing computer work, not as evidence that a new operating system is in development.
session management software for desktops
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
Is “Make Tmux the OS” announcing a new operating system?
No. The author describes it as a thought exercise. The supplied material does not announce software, a release or a development team.
What does the author mean by making tmux the OS?
The idea is to bring tmux’s persistent, detachable, task-oriented sessions to a desktop interface designed for people who do not use terminal tools.
What desktop problems does the post identify?
It focuses on manually rearranging windows when screens change, differences in how people organize windows, the separation of browser tabs from other work, and information stored within applications rather than conventional files.
Does the source explain how the proposed system would work?
Not fully. The excerpt mentions a concept called WindowScape, but does not give enough information to assess its design or implementation.
What remains unknown?
There is no confirmed prototype, schedule, platform support or evidence that the approach has been tested with users. The supplied material also does not provide enough detail to assess how it would protect private content on shared displays.
Source: hn
Fall Picks
fall essentials
As an affiliate, we earn on qualifying purchases.
