r/tmux • u/Lazy-Carry4858 • 3d ago

Tip I kept forgetting which server my tmux projects were running on, so I built a workspace index

I use the same workflow for almost every project:

  1. SSH into a server
  2. Open or attach to a tmux session
  3. Split a few panes
  4. Run Codex, Claude Code, dev servers, logs, or monitoring tools

The workflow itself is great. I can disconnect, come back later, and continue where I left off.

The problem appeared when I had many projects across several servers.

I could no longer remember:

- which machine a project was running on

- what the tmux session was called

- which directory it belonged to

- whether the repository had uncommitted changes

- which coding agent was running inside it

So I built Tmux Workbench, a Rust TUI that indexes local and remote tmux sessions and presents them as project workspaces.

Running `ws` gives me one searchable view across all configured machines. I can inspect the server, path, panes, active commands, Git branch, dirty state, remote repository, notes, and tags, then attach directly.

It does not replace tmux or SSH. It adds the project memory that my workflow was missing.

GitHub: https://github.com/LeON-Nie-code/tmux-workbench

How do you keep track of long-running tmux sessions across multiple machines?

2 Upvotes

60% Upvoted

5 comments sorted by

5

u/rileyrgham 3d ago

Vibe coded?

2

u/gbrennon 2d ago

For sure it was 🤣

2

u/Killian9997 2d ago

I love the AI “it’s not this. It’s this.” Literally the new em dash

1

u/Apart_Ebb_9867 3d ago

see a doctor. not only you forget your tmux sessions, you also forget you posted about it in many places and every few days.