tmux

Send keystrokes and scrape pane output from tmux sessions.

3|1|Updated Jan 29, 2022
One-click install
npx skills add https://github.com/r0man/guix-home --skill tmux-r0man
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tmux
Source: https://github.com/r0man/guix-home/tree/main/modules/r0man/guix/home/files/claude-code/skills/tmux
Command: npx skills add https://github.com/r0man/guix-home --skill tmux-r0man

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires tmux, bash, jq, and includes references (resource) components.

What problem does it solve?

This Skill enables programmable control of tmux sessions to drive interactive CLIs (Python, gdb, ipdb, psql, mysql, node), automate terminal tasks, and streamline debugging.

Core Features & Use Cases

  • Session Registry & Auto-Detection: Track and reuse sessions automatically to reduce boilerplate.
  • Safe Input & Monitoring: Send commands with reliability and monitor pane outputs.
  • Interactive Debugging: Automate Python REPL, gdb, ipdb, and other shells.
  • Session Lifecycle Guidance: Lifecycle docs help you start, reuse, and cleanup sessions.

Quick Start

Start a Python REPL session named claude-python and run a command via a script, then monitor the session with the provided helper.

Frequently Asked Questions about tmux

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

FAQPage Schema
How do I automate control of tmux sessions to debug interactive CLIs?

Automate tmux sessions by sending keystrokes and scraping pane output to drive interactive CLIs like Python, gdb, ipdb, psql, mysql, and node. This Skill provides session registry, safe input delivery, and prompt waiting to streamline debugging workflows without manual terminal interaction.

Can I automate debugging in Python REPL and other interactive shells?

Yes. This Skill automates Python REPL, gdb, ipdb, and other interactive shells by programmatically sending commands, monitoring output, and managing session lifecycle. Register sessions by name for reuse across scripts and reduce boilerplate for repetitive debugging tasks.

How do I track and reuse tmux sessions across multiple scripts?

Register tmux sessions in a JSON registry that persists session names and sockets. Auto-detect or explicitly resolve sessions to avoid recreating them on each script run, reducing overhead and enabling reliable multi-session management on Linux and macOS.

What's the safest way to send commands to tmux panes and read output?

Send commands reliably using safe input delivery with prompt waiting to detect when commands complete. Scrape pane output directly to validate results and monitor session health, avoiding race conditions and silent failures in automated terminal workflows.

Does this work for automating multi-session terminal workflows?

Yes. Manage multiple tmux sessions on Linux and macOS using stock tmux with private sockets. The Skill handles session lifecycle, health monitoring, and atomic registry updates to coordinate complex terminal automation across separate sessions.

What dependencies do I need to run tmux automation?

Stock tmux, bash, and jq are required. These tools enable session control, command execution, and JSON registry parsing without additional installations, making tmux automation lightweight and portable across standard Unix environments.