wtf is tmux-workbench?

Tmux Workbench is a command-line tool that helps developers keep track of their work when they are juggling many terminal sessions across multiple machines. It builds on top of tmux, a common tool for keeping terminal sessions running in the background, and ssh, the standard way to connect to remote servers. On its own, tmux does not remember much context once you disconnect: this tool adds a memory layer on top so you can quickly find, inspect, and jump back into any session. It works by scanning your local and remote tmux sessions and recording useful details about each one: which server it is on, what project folder and command it is running, the git branch, commit, and whether there are uncommitted changes, plus any AI coding agent instruction files like CLAUDE.md or AGENTS.md found in that folder. All of this is stored locally in a small database, and you can add your own notes, nicknames, and tags to each session as well. The tool pays particular attention to sessions running AI coding agents such as Claude Code, Codex, Gemini, or Aider, treating those as important workspace context and showing their instruction files directly in its interface. You interact with it through a single command called ws, either using specific subcommands from the terminal or a full-screen browsable interface with search and filtering. A recreate command can even rebuild a missing tmux session from its last known snapshot, prefilling commands in the right panes without automatically running them. Installation is done with a one-line install script, through Rust's Cargo package manager, via Homebrew, or by downloading a prebuilt binary directly. Session and configuration data live in a local SQLite database and a YAML config file. The project is built in Rust and is still pre-1.0, meaning its command layout and stored data format may still change before a stable release. It is licensed under MIT.