tmux

Start isolated tmux sessions, send keystrokes, and capture pane output.

58|1|Updated May 13, 2026

Search Tags:#tmux #terminal automation #coding agents #interactive cli #keystroke control #pane output capture

Ready to run

npx skills add https://github.com/Simplified-Reasoning/Pi-Bench --skill tmux-simplified-reasoning

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tmux
Source: https://github.com/Simplified-Reasoning/Pi-Bench/tree/main/third_party/nanobot/nanobot/skills/tmux
Command: npx skills add https://github.com/Simplified-Reasoning/Pi-Bench --skill tmux-simplified-reasoning

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

You need to run and supervise interactive command-line programs (REPLs, TUIs, coding agents) from an automated environment, while still being able to send input and read output reliably.

Core Features & Use Cases

Remote keystroke control: Start a tmux session on an isolated socket and drive programs by sending keystrokes to specific panes.
Output scraping for monitoring: Capture recent pane history to detect prompts, completion, and logs without manual terminal attachment.
Multi-agent orchestration: Run multiple parallel coding or REPL workloads in separate tmux sessions and poll for completion.
Use Case: You want to run several coding agents (e.g., Codex/Claude Code) against different repos at the same time, then collect outputs from whichever sessions finish first.

Quick Start

Start a detached tmux session on an isolated socket and then open a monitoring view by attaching to that session for interactive inspection.

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 and send keystrokes to a detached terminal session?▼

You can control interactive CLI workflows remotely by starting an isolated tmux session, sending keystrokes to specific panes via send-keys, and capturing pane output to monitor program state without manual terminal attachment.

What is the best way to run multiple coding agents in parallel and poll for completion?▼

Running multiple coding agents in parallel is achieved by opening separate tmux sessions on isolated sockets for each workload, then polling pane output with regex and text-based timeouts to detect which sessions finish first.

How do I capture terminal output from a REPL or TUI to detect prompts and logs in an automated environment?▼

Capturing terminal output from a REPL or TUI involves scraping recent pane history from a tmux session to detect prompts, completion signals, and logs without requiring an interactive terminal attachment.

Can I use tmux send-keys to drive TTY-dependent programs safely without session conflicts?▼

Yes, you can drive TTY-dependent programs safely by starting tmux on an isolated socket directory, which ensures deterministic pane targeting and prevents keystroke conflicts with other concurrent terminal sessions.

Does terminal automation with tmux work for orchestrating multiple REPLs across different repositories?▼

Terminal automation with tmux supports orchestrating multiple REPLs or coding agents across different repositories by allocating separate panes or sessions, sending targeted keystrokes, and monitoring each output stream independently.