tmux

Manage persistent tmux sessions for long-running shell tasks.

1.3k|179|Updated Feb 3, 2025
One-click install
npx skills add https://github.com/Team-Commonly/commonly --skill tmux-team-commonly
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tmux
Source: https://github.com/Team-Commonly/commonly/tree/main/backend/commonly-bundled-skills/tmux
Command: npx skills add https://github.com/Team-Commonly/commonly --skill tmux-team-commonly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

tmux enables running and managing long-running shell tasks by keeping sessions detached and persistent across tool calls, so you can start a task, disconnect, and reattach later without losing progress.

Core Features & Use Cases

  • Persistent sessions: create detached sessions that survive tool-call boundaries.
  • Detach/attach workflow: rejoin work with ongoing processes and outputs.
  • Output capture: view logs and stdout from active sessions without blocking the main flow.
  • Use Case: long builds, iterative testing, or long-running scripts that require pause-and-resume.

Quick Start

Start a new detached session named "build" and later attach to review progress.

Frequently Asked Questions about tmux

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

FAQPage Schema
How do I keep long-running shell tasks persistent across tool calls?

To keep long-running shell tasks persistent, use detached sessions that survive across boundaries. Start a task in a named session, disconnect, and reattach later to resume work without losing progress or output.

What is the best way to tail logs without blocking the main terminal workflow?

The best way to tail logs without blocking is using output capture within detached sessions. View stdout and logs from active background processes, then disconnect to continue other work in the main flow.

How do I pause and resume iterative builds or long-running scripts?

Pause and resume iterative builds by starting them in a detached, persistent session. Disconnect after initiating the build and reattach to the named session later to review progress and output.

Can I view stdout from active sessions without blocking my current process?

Yes, output capture lets you view stdout from active sessions without blocking. Rejoin ongoing processes inside detached sessions to inspect logs and outputs while your current process continues running.

Why does my terminal session lose progress when disconnecting from long builds?

Terminal sessions lose progress when disconnecting because standard shells terminate on exit. Detached, persistent sessions prevent this by surviving tool-call boundaries, allowing you to reattach to ongoing builds later.

Do I need any dependencies to orchestrate persistent terminal sessions?

No dependencies are required to orchestrate persistent terminal sessions. The session management capability operates independently to support creation, naming, detaching, attaching, and output capture for task orchestration.