Tmux Session Manager

A unified tmux session management system with three entry points: tm (current directory), ts (sessionizer/directory picker), and tma (attach to any session). Supports per-project JSON configs for reproducible multi-session setups.

Inspired by ThePrimeagen's tmux-sessionizer.

Requirements

• tmux — terminal multiplexer
• fzf — fuzzy finder for interactive menus
• jq — JSON parser for project configs

Optional (for multi-session workspace support):

• A terminal emulator that supports detached spawning (default: kitty)
• A tiling WM with workspace commands (default: Hyprland)

Installation

git clone https://github.com/HRmemon/tmux-session-manager.git
cd tmux-session-manager

# Add to PATH (pick one)
export PATH="$PWD:$PATH"                              # temporary
ln -s "$PWD/tm" ~/.local/bin/tm                        # symlink each entry
ln -s "$PWD/ts" ~/.local/bin/ts
ln -s "$PWD/tma" ~/.local/bin/tma

File Structure

tmux-session-manager/
├── tm              # Wrapper → tmux-manager (current dir mode)
├── ts              # Wrapper → tmux-manager (sessionizer mode)
├── tma             # Wrapper → tmux-manager (list & attach mode)
├── tmux-manager    # Unified dispatcher (dispatches on $0)
├── tmux-core.sh    # Shared library (sourced, not executed)
└── tmux-rofi.sh    # Optional rofi frontend (alternative to fzf)

Features

Feature	Description
Quick sessions	Create N windows in current dir with tm -q 3
Multiple sessions per dir	Auto-increments: project, project_2, project_3
Project configs	JSON file defines multi-session setups with commands
Workspace integration	Move terminal to WM workspace (pluggable)
Template generation	Auto-detect subdirs and create starter JSON
Attach-or-create	PROJECT options attach to existing sessions instead of recreating
Attach to any session	tma lists all running sessions with fzf preview
Open in new terminal	Ctrl-o on any session — spawns a new terminal instead of switching
Kill sessions	Ctrl-d in tma — kills a session with confirmation

Usage

tm — Current Directory Mode

tm                 # Interactive menu (default 2 windows)
tm 3               # Menu, NEW creates 3 windows
tm -q              # Quick: skip menu, create 2 windows
tm -q 4            # Quick: create 4 windows
tm 3 -w 5          # Menu, move to workspace 5
tm -q 2 -w 9       # Quick: 2 windows on workspace 9

ts — Sessionizer Mode

ts                    # fzf to pick dir, then interactive menu
ts ~/projects/foo     # Skip picker, go straight to menu
ts -q                 # Pick dir, quick create (no menu)
ts -q ~/projects/foo  # Quick create in specified dir

tma — List & Attach

tma                   # fzf list of all sessions, pick one to attach

Key	Action
Enter	Attach/switch to session
Ctrl-o	Open session in a new terminal
Ctrl-d	Kill session (with confirmation)

Interactive Menu (tm / ts)

When running tm or ts, the fzf menu shows:

ATTACH: project           ← Existing sessions for this dir
ATTACH: project_2
NEW: Quick session (2 windows)
───────────────────────────────────
PROJECT: ALL (spin up everything)    ← If JSON config exists
PROJECT: project-dev
PROJECT: project-servers
───────────────────────────────────
GENERATE: Create tmux_sessions.json  ← Template generator

Key	On ATTACH / NEW / PROJECT
Enter	Attach/switch as usual
Ctrl-o	Open session in a new terminal instead

Project Configuration

For projects you work on repeatedly, create a tmux_sessions.json in the project root.

Example

[
  {
    "name": "myapp-dev",
    "workspace": 4,
    "windows": [
      { "name": "editor", "path": ".", "command": ["nvim"] },
      { "name": "backend", "path": "backend", "command": [] },
      { "name": "frontend", "path": "frontend", "command": [] }
    ]
  },
  {
    "name": "myapp-servers",
    "workspace": 9,
    "windows": [
      { "name": "api", "path": "backend", "command": ["npm run dev"] },
      { "name": "web", "path": "frontend", "command": ["npm run dev"] },
      { "name": "db", "path": ".", "command": ["docker compose up db"] }
    ]
  }
]

Field Reference

Field	Type	Required	Description
name	string	yes	Session name
workspace	number	no	WM workspace to move to
root	string	no	Root path relative to JSON file (default: .)
windows	array	yes	List of window definitions
windows[].name	string	yes	Window name
windows[].path	string	no	Path relative to root (default: .)
windows[].command	string or array	no	Command(s) to run on window open

Command Field

The command field supports both formats:

// Single command (string)
{ "command": "nvim" }

// Multiple commands (array) — runs sequentially
{ "command": ["source .venv/bin/activate", "python manage.py runserver"] }

// Empty (no command)
{ "command": [] }
{ "command": "" }

PROJECT: ALL Behavior

When selecting "ALL":

1. First session attaches in current terminal (moves to its workspace)
2. Subsequent sessions open in new terminal windows on their respective workspaces

If a session is already running, it attaches instead of recreating.

Customization

Search Directories (for ts)

Edit tmux-core.sh and modify the TMUX_SEARCH_DIRS array:

TMUX_SEARCH_DIRS=(
    ~/projects
    ~/work
    ~/.config
)

Window Manager / Terminal Integration

The workspace and terminal-spawning logic is contained in two functions at the top of tmux-core.sh. Override them to match your setup.

move_to_workspace

Moves the focused window to a workspace. Default: Hyprland.

# i3 / sway
move_to_workspace() {
    local workspace="$1"
    i3-msg workspace "$workspace"     # or: swaymsg workspace "$workspace"
}

# No workspace management (disable)
move_to_workspace() { :; }

open_terminal_with_session

Opens a new terminal attached to a tmux session. Default: kitty.

# Alacritty
open_terminal_with_session() {
    local session_name="$1"
    local workspace="$2"
    if [[ -n "$workspace" && "$workspace" != "null" && "$workspace" != "" ]]; then
        alacritty --title "$session_name" -e sh -c "
            move_to_workspace $workspace
            tmux attach -t \"$session_name\"
        " &
    else
        alacritty --title "$session_name" -e tmux attach -t "$session_name" &
    fi
}

# Wezterm
open_terminal_with_session() {
    local session_name="$1"
    wezterm start -- tmux attach -t "$session_name" &
}

Template Generation

The GENERATE option scans for subdirectories and creates a starter JSON:

• Skips: node_modules, .git, .venv, venv, env, __pycache__, dist, build, .next, .cache, coverage, tmp
• Creates two sessions: {project}-dev (with nvim) and {project}-servers (empty commands)

Session Naming

Sessions are named after the directory:

• Spaces and dots become underscores: my project → my_project
• Multiple sessions: project, project_2, project_3, ...

Extending

Adding a new menu option

1. Edit build_menu_options() in tmux-core.sh
2. Add your option string to the options array
3. Handle it in execute_menu_action() with a new case branch

Adding a new entry point

1. Symlink tmux-manager to a new name (e.g., ln -s tmux-manager mycmd)
2. Add a mycmd_mode() function and a new case in the dispatch at the bottom of tmux-manager

Adding a new flag to tm or ts

1. Add argument parsing in the while [[ $# -gt 0 ]] loop inside tm_mode() or ts_mode() in tmux-manager
2. Pass the value to run_interactive_menu or handle in quick mode

Troubleshooting

Problem	Fix
Session creates infinite windows	Ensure jq is installed and JSON is valid: jq . tmux_sessions.json
Workspace not switching	Check your WM command. Override move_to_workspace()
Menu not showing	Check if fzf is installed: which fzf
Commands not running	Check command array syntax. Each element runs with Enter after it

License

MIT