Maximize the windows
Why Termany nests workspaces, vertical tabs, and horizontal tabs — and how persistent sessions change the way you context-switch.
Every terminal power user ends up fighting the same battle: too many live shells, not enough structure. Tabs multiply until their titles truncate into uselessness; tmux sessions pile up until tmux ls reads like an archaeology dig. The shells aren't the problem — the organization is.
Termany's answer is a three-level hierarchy, and each level maps to how you already think:
Workspace — a whole context
The far-left rail. One workspace per client, per product, per life-area. Switching workspaces swaps everything below it — you're not hunting for the right tab among thirty, you're stepping into a different room.
Vertical tab — a project inside it
The left sidebar. Inside a product workspace you might have api, web, infra, docs. Each vertical tab owns its own set of shells, so the mental model stays clean: this column of the screen is that project.
Horizontal tab — one live shell
The top strip. server, build, db, logs, agent — one persistent session each. And persistent is the key word:
A build in one tab survives you switching away. It keeps running, keeps its scrollback, and keeps its place.
That single property changes context-switching from "pause everything, remember state, resume later" to just… looking somewhere else for a while.
Driven from the keyboard
The hierarchy is only worth it if navigating it is free:
| Key | Action | | --- | -------------------- | | ⌘T | New horizontal tab | | ⌘N | New vertical tab | | ⌘⇧N | New workspace | | ⌘W | Close horizontal tab |
Split panes inside a tab — the true "max windows" grid — are next on the roadmap, alongside session reconnect that survives a page reload.
Want to feel it? The homepage demo runs the real UI in your browser.