Use case · Claude Code
A terminal for Claude Code power users
Once Claude Code becomes how you work, one session turns into five. Termany is built for that point: every session gets a persistent pane, and the one that needs you rises to the top.

The problem: tab hunting
Five Claude sessions in five terminal tabs means constantly clicking through them to see which one finished, which one is asking for permission, and which one is still thinking. Context about branches, ports, and cost lives somewhere else entirely.
How Termany helps
Termany tags each pane working, done, or needs attention by reading its foreground job and the changes on screen — it works with Claude Code’s own interface. Tagged panes collect in the ACTIVE section above the page tree, so the session that stopped is one click away.
- Workspace → page → tab → pane, with every tab a persistent session
- ⌘P jumps to any page, tab, or pane by name
- ⌘M maximizes one pane over a dimmed background
A typical day
Open a page per project and give each Claude session its own pane.
- Launch Claude from the right rail into a split (⌘D)
- Open the Git diff beside it (⌥⌘G) to review what it changed
- Resume yesterday’s conversation from session history (⇧⌘H), grouped by branch
- Check estimated cost and tokens by project in the usage view (⇧⌘U)
What it doesn’t do
Termany does not replace Claude Code or proxy its model calls. It runs your installed, authenticated claude CLI and reads its transcripts locally. Cost figures are estimates from those transcripts.
Frequently asked questions
Does Termany work with my Claude Max or Pro subscription?
Termany runs the Claude Code CLI you already installed and signed in to, so it uses whatever account that CLI uses.
How many Claude sessions can I run?
There is no built-in limit on panes. Practical limits come from your machine and your Claude plan.
Do sessions survive switching tabs?
Yes. Every tab is a persistent session that keeps running, with its scrollback, while backgrounded.