tmux

Send keystrokes and capture pane output from tmux sessions.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/voznik/dotfiles --skill tmux-voznik
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tmux
Source: https://github.com/voznik/dotfiles/tree/main/.rulesync/skills/tmux
Command: npx skills add https://github.com/voznik/dotfiles --skill tmux-voznik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automate and orchestrate interactive terminal work by remotely controlling tmux sessions, sending keystrokes, and capturing pane output.

Core Features & Use Cases

  • Remote session management: spawn and manage multiple tmux sessions and windows for parallel CLI tasks.
  • Input and output automation: send keys, read pane content, wait for prompts, and aggregate results across sessions.
  • Use Case: debugging concurrent scripts, running coding agents in parallel, and monitoring long-running interactive tasks.

Quick Start

Connect to a running tmux socket and start sending keystrokes to a session.

Frequently Asked Questions about tmux

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

FAQPage Schema
How do I automate interactive CLI workflows with tmux session management?

You can automate interactive CLI workflows with tmux session management by remotely controlling sessions to send keystrokes, wait for prompts, and capture pane output across multiple parallel terminal tasks.

Can I run parallel coding agents in separate terminal sessions and capture their output?

Yes, you can run parallel coding agents in separate terminal sessions by spawning multiple tmux sessions and windows, sending input keystrokes, and aggregating the captured pane output from each session.

How does sending keystrokes and capturing pane output work for remote tmux control?

Remote tmux control works by connecting to a running tmux socket and using a defined interface to safely send input keystrokes to targeted panes and capture their resulting terminal output for automation.

What's the best way to monitor long-running interactive tasks across multiple terminal panes?

The best way to monitor long-running interactive tasks is by orchestrating remote tmux sessions to manage multiple windows, send automated keystrokes, and capture pane content to track concurrent script execution.

Do I need a specific tmux socket configuration to start sending commands to parallel sessions?

You need a running tmux socket available on PATH to connect and start sending keystrokes, with the internal interface handling socket management, pane targeting, and safe input and capture commands.

Why use tmux session orchestration instead of standard shell scripts for debugging concurrent scripts?

Tmux session orchestration handles interactive CLI requirements that standard shell scripts cannot, allowing you to send keystrokes to live panes, wait for prompts, and capture real-time output during concurrent script debugging.