tmux

Manage tmux sessions, tmuxinator templates, and sesh workspaces.

2|Updated Sep 9, 2024
One-click install
npx skills add https://github.com/trentshaines/dotfiles --skill tmux
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tmux
Source: https://github.com/trentshaines/dotfiles/tree/main/dot_claude/skills/tmux
Command: npx skills add https://github.com/trentshaines/dotfiles --skill tmux

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing multiple terminal windows, processes, and persistent sessions can be cumbersome. This Skill streamlines your terminal workflow by helping you create, manage, and switch between tmux sessions and tmuxinator project templates, ensuring your work environment is always ready.

Core Features & Use Cases

  • Session Management: Create, list, attach to, and kill tmux sessions with ease.
  • Project Templates: Automate complex multi-pane layouts for specific projects using tmuxinator.
  • Use Case: You're starting a new project and need a specific terminal layout with nvim in one pane, a shell in another, and claude --resume in a third. Ask Claude to create a new tmuxinator template for your project, and it will guide you through the setup.

Quick Start

I need to create a new tmuxinator template for my 'backend-api' project. It should have three panes: one for nvim, one for a shell, and one for docker compose up.

Frequently Asked Questions about tmux

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage multiple terminal sessions without losing my workspace?

Terminal session management with tmux creates persistent multiplexed workspaces that survive disconnections. You can create named sessions, attach and detach at will, and return to the exact state later—ideal for long-running development, monitoring, and remote work where you need multiple panes and windows organized by project.

Can I automate terminal layouts for my projects using templates?

Yes, tmuxinator templates let you define YAML-based project layouts with predefined pane and window configurations. Instead of manually recreating multi-pane setups each time, you specify your tools—nvim, shells, docker commands—once in a template and launch the entire layout with a single command.

How do I switch between tmux sessions efficiently in my shell workflow?

Zsh integration enables fast session switching through shell functions. Rather than typing attach commands manually, you can list, fuzzy-find, and jump between sessions directly from your prompt, streamlining navigation across development, monitoring, and dotfiles workflows.

What's the difference between tmux sessions and window layouts?

Sessions are independent workspace containers that persist across disconnections and hold multiple windows. Windows organize panes within a session. Tmuxinator templates pre-configure both—defining session structure, window count, pane splits, and startup commands for reproducible project environments.

Can I use tmux with 1-based pane indexing and custom root paths?

Yes, this Skill supports 1-based pane indexing configuration and session root/path awareness. You can set the working directory for each pane and customize indexing to match your preference, ensuring panes launch in the correct project context.

Why use terminal multiplexing instead of opening separate terminal windows?

Terminal multiplexing consolidates multiple panes and windows in a single session, reducing clutter and enabling persistent state. Sessions survive network drops and system sleeps, processes keep running detached, and predefined layouts reduce setup time for complex workflows.