pairmux

Drive interactive CLI programs within persistent tmux sessions using JSON envelopes.

6|Updated Jul 19, 2026

Search Tags:#automation #interactive #tmux #terminal #shell #pty

Ready to run

npx skills add https://github.com/treeleaves30760/pairmux-skills --skill pairmux

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pairmux
Source: https://github.com/treeleaves30760/pairmux-skills/tree/main/skills/pairmux
Command: npx skills add https://github.com/treeleaves30760/pairmux-skills --skill pairmux

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the inability of standard agentic shell tools to interact with PTY-based programs like REPLs, TUIs, pagers, and password prompts, while providing a robust mechanism for human-in-the-loop collaboration.

Core Features & Use Cases

Persistent Terminal Sessions: Maintains live tmux-backed PTYs that preserve shell state (venv, exports, nvm) across multiple commands.
Blocking Execution Loop: Provides deterministic run and wait commands that return on specific outcomes rather than relying on unreliable sleep-and-guess timing.
Human-in-the-loop: Enables secure handoffs for secret prompts and allows human observation or intervention in the same live terminal session.

Quick Start

Use the pairmux skill to open a new terminal named build and run a long-lived make command inside it.

Frequently Asked Questions about pairmux

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

FAQPage Schema

How do I automate interactive terminal sessions and CLI programs with persistent shell state?▼

Automating interactive terminal sessions requires reliable PTY primitives that maintain live shell state like venv and exports. Using tmux-backed persistent sessions allows deterministic blocking execution for driving long-running processes without sleep-and-guess timing.

Can I handle password prompts and secret inputs in automated shell workflows?▼

Handling password prompts in automated shell workflows requires secure human-in-the-loop handoffs. By driving PTY-based programs within shared tmux sessions, humans can observe or intervene to securely provide secret inputs during blocking execution.

What is the best way to run long-lived processes and wait for specific outcomes in an agentic workflow?▼

Running long-lived processes deterministically requires blocking execution loops that return on specific outcomes rather than relying on unreliable sleep timing. Persistent tmux sessions provide the reliable PTY environment needed for complex agentic workflows.

Does tmux support shared terminal observation for human and agent collaboration?▼

Tmux supports shared terminal observation by maintaining live PTY sessions that multiple participants can view. This enables human-in-the-loop intervention and secure handoffs while the agent drives interactive CLI programs.

Why does my automated script fail to interact with REPLs and TUIs?▼

Automated scripts fail with REPLs and TUIs because standard shell tools lack PTY interaction capabilities. Driving these interactive programs requires persistent terminal primitives that facilitate machine-readable JSON envelopes for robust error handling.