tmux

Control tmux sessions to drive interactive command-line tools and capture output.

17|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/ivanrvpereira/.agents --skill tmux-ivanrvpereira
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tmux
Source: https://github.com/ivanrvpereira/.agents/tree/main/skills/tmux
Command: npx skills add https://github.com/ivanrvpereira/.agents --skill tmux-ivanrvpereira

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill solves the challenge of driving interactive CLI programs (like Python REPLs and debuggers) reliably while capturing their live output for later review.

Core Features & Use Cases

  • Remote session control: Start isolated tmux sessions and send keystrokes to automate interactive workflows.
  • Pane output capture: Scrape recent pane history (or poll via a helper) to detect prompts and progress without guessing timing.
  • Safe isolation and targeting: Use a private tmux socket and consistent pane targeting so the automation doesn’t interfere with a user’s existing tmux.

Quick Start

Start an isolated tmux session for an interactive workflow by creating a private socket directory, launching a new session, sending your first command, and then monitoring the pane with a copy/paste attach command.

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 programs and capture their live output?

You can automate interactive CLI programs by using a private tmux socket to send deterministic keystrokes and poll pane output with regex. This isolates the workflow and captures live output for review without guessing execution timing.

How do I control a Python REPL or gdb session programmatically?

Control a Python REPL or gdb session by launching it in an isolated tmux session, sending keystrokes to execute commands, and synchronizing on detected prompts via regex polling of the pane history.

What is the best way to scrape terminal output without interfering with my existing tmux sessions?

The best way to scrape terminal output safely is using a private tmux socket and consistent pane targeting. This creates an isolated environment that prevents automation scripts from interfering with your existing tmux sessions.

Can I poll pane history to detect when an interactive command finishes?

Yes, you can poll pane history with regex to detect prompts and progress accurately. This removes the need to guess execution timing by synchronizing directly on the terminal output patterns.

How do I clean up tmux sessions to avoid lingering servers after automation?

Clean up tmux sessions by explicitly targeting the isolated private socket used for the automation and terminating the session. This ensures no lingering servers remain after the interactive workflow completes.