macOS · native window over tmux

MTW Tmux

See what is running in your tmux sessions without attaching to each one.

Download for MacFree, MIT licence
pane 1
$ npm run dev
ready in 412ms
pane 2
$ tail -f app.log
…streaming
pane 3
$ pytest -q
42 passed
pane 4
$ claude
agent active
pane 5
$ git status
clean
pane 6
$ tmux ls
6 sessions

A native window over your tmux servers: which sessions exist, what runs in each pane, for how long, and what changed. With notifications when a process finishes or stalls.

The problem

Silent until you attach

tmux tells you nothing until you attach. With six sessions open, you find out one died two hours ago when you finally get to it.

And tmux ls gives you a list of names, not what is actually running inside.

How it works

From your tmux server to a panel on your screen.

01See everythingMTW Tmux gives you one window over all of it: every session with its windows and panes, what command is running, since when, and whether it has gone idle. You can send commands, see a live preview of the content, or attach in Terminal with one click.
02Read the stateIt reads state through tmux's control mode rather than by polling, so changes show up when they happen instead of at the next check. If control mode is unavailable it falls back to polling and reconnects on its own.
03ReactYou can define rules that fire on an event: a notification when a process ends, a command sent automatically, a script run. Each with a cooldown and a log, so you do not end up with a hundred notifications.
04Claude Code readsIt also ships an MCP server so Claude Code can read your session state. Six verbs, all read-only — it cannot kill, create or send keys anywhere. It works with the app closed.
// screens

The app's screens

MTW Tmux puts every tmux session in one window, each with its windows, its age and its folder, and marks a session left detached too long as idle.
Open a session to see the command in every pane on a map of the layout, and click a pane to preview its content without attaching.
With the Scanner in tmux control mode, changes show up as they happen. If control mode drops, it keeps checking sessions on a timer and reconnects on its own.
Once you switch auto-commands on, Scanner rules fire on an event such as a closed session and send a notification, keys or a shell command, each with a cooldown and a log of what ran.
// screen tour

What each screen shows

  1. 01 / 04

    The dashboard: the whole server at a glance

    • At the top, the state of the tmux server: whether it is running, how many sessions, windows and panes it has, the tmux version and the prefix.
    • Each session shows its window count, its age, its folder and whether it is attached or detached.
    • A session left detached for more than 24 hours, by default, is marked idle, and “Clean idle” closes them all after you confirm.
    • “Attach” opens the session in the terminal picked at the top: Terminal, iTerm, Ghostty, WezTerm or Alacritty.
  2. 02 / 04

    An open session: the pane map

    • Four tabs: the windows with their panes, the preview, sending commands, and activity.
    • The map shows how the panes are laid out in the window, and clicking a pane shows its content without attaching.
    • For every pane you see the command, the directory, the size and the pid.
    • The preview is a snapshot you reload with a button, and a pane's full scrollback can be exported to a file.
  3. 03 / 04

    The Scanner: a log of what changed

    • Each line is an event with its time: a session or a window opened or closed.
    • By default the Scanner checks on a timer. Here it runs in tmux control mode, chosen in Settings, so changes show up as they happen.
    • If control mode drops, it keeps checking sessions on a timer and reconnects on its own.
    • The log can be filtered by text and emptied with “Clear”.
  4. 04 / 04

    Rules: what happens on an event

    • At the top is the auto-commands switch. It is off by default and, until you turn it on, no rule runs; after that, rules run while the Scanner is running.
    • Each rule ties an event, such as a session closed or a window opened, to an action: a notification, keys sent to the session, or a shell command.
    • A rule can filter on the event's text, like “lint” in the frame, and wait a cooldown between two firings.
    • “Recent executions” shows what ran, when, and on which event.
What it does

One window over everything running

Native window

  • Every session, window and pane in a single view
  • Live state through tmux control mode, not repeated polling
  • Falls back to polling and reconnects on its own if control mode drops
  • Preview each pane's content without attaching to it
  • Interactive map of the pane layout

Automation

  • Rules that fire on an event, with a cooldown and a log
  • Session templates, saveable from a session you already have
  • A cheat sheet that reads your real prefix from your own config

MCP & localization

  • Bundled MCP server: six verbs, all read-only, works with the app closed
  • Interface in Romanian and English
Download

MTW Tmux for Mac

MTW Tmux is free, under the MIT licence: there is nothing to buy and nothing to activate.

Built with
SwiftSwiftUItmuxMCP

Download the app

Download version 0.8.2

3.7 MB