tmux

Manage concurrent processes in tmux windows and capture output.

16|Updated Aug 29, 2025
One-click install
npx skills add https://github.com/sourcegraph/amp-contrib --skill tmux-sourcegraph
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tmux
Source: https://github.com/sourcegraph/amp-contrib/tree/main/tmux
Command: npx skills add https://github.com/sourcegraph/amp-contrib --skill tmux-sourcegraph

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you orchestrate multiple concurrent processes (servers, watchers, or long tasks) by creating and managing tmux windows/panes directly from the Bash tool, keeping your main chat channel unblocked.

Core Features & Use Cases

  • Window Management: Spawn new windows or panes for separate tasks.
  • Command Dispatch: Send commands to those windows without switching context.
  • Output Inspection: Capture and view output from any task window.

Quick Start

  • Start a new window: tmux new-window -n server -d
  • Run a command in that window: tmux send-keys -t "server" "npm start" C-m
  • Inspect output: tmux capture-pane -p -t "server"

Frequently Asked Questions about tmux

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

FAQPage Schema
How do I run multiple long-running processes in separate terminal windows without blocking my main workflow?

tmux lets you create and manage multiple concurrent processes in separate windows within a single session. You can spawn dedicated windows for servers, watchers, and builds, then send commands and inspect output without leaving your main channel—keeping your workflow unblocked and organized.

Can I send commands to a tmux window and capture its output programmatically?

Yes. tmux lets you dispatch commands to named windows using send-keys, then retrieve current and scrollback output with capture-pane. This enables automation of multi-process task orchestration directly from scripts or automation tools.

How do I spawn and manage separate tmux windows for different tasks like servers and watchers?

Create named windows with new-window, send commands to each using send-keys, and inspect their state with capture-pane. This approach separates concerns—each task runs independently in its own window while remaining accessible from a single session.

What's the difference between managing processes manually versus using tmux for concurrent task orchestration?

Manual process management requires switching contexts and monitoring separate terminals. tmux centralizes control: create windows, dispatch commands, and capture output all from one session, eliminating context switching and enabling reproducible automation of multi-process workflows.

Do I need to verify tmux is available before creating windows and sending commands?

Yes. The Skill includes verification of tmux presence as a functional requirement before attempting window creation or command dispatch. This ensures your automation doesn't fail mid-workflow due to missing dependencies.