tmux

Manage persistent tmux sessions with send-keys, capture-pane, and pipe-pane commands.

1|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/antonyfmunoz/OS --skill tmux-antonyfmunoz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tmux
Source: https://github.com/antonyfmunoz/OS/tree/main/skills/tools/tmux
Command: npx skills add https://github.com/antonyfmunoz/OS --skill tmux-antonyfmunoz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

tmux solves the problem of losing terminal state when SSH sessions disconnect or your terminal closes, by keeping long-running processes in a persistent server that you can detach from and reattach to.

Core Features & Use Cases

  • Persistent sessions for long-running work: keep agents, builds, and background tasks alive across reconnects and crashes.
  • Scriptable command/control: drive panes programmatically with verbs like send-keys, capture-pane, and pipe-pane.
  • Structured pane/window/session hierarchy: manage concurrent workflows using stable targets and IDs for automation and debugging.
  • EOS-style logging & orchestration: continuously pipe pane output to files for ingestion, and respawn dead panes for self-healing loops.

Quick Start

Pin an EOS tmux server session and run your agent in a named detached session by telling the AI: “Create a detached tmux session named eos-main on socket -L eos in /opt/OS, sized for log scraping, and then run python3 -m eos_ai.cognitive_loop in pane 0.”

Frequently Asked Questions about tmux

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

FAQPage Schema
How do I keep long-running terminal agents alive after an SSH session disconnects?

Terminal multiplexing keeps long-running agents alive by running them inside a persistent tmux server. You can safely detach from the SSH session and reattach later without losing the executing state.

What is the best way to automate command execution across multiple terminal panes?

Automating command execution across terminal panes is achieved using the send-keys command verb. This allows programmatic control to drive concurrent workflows within a structured window and session hierarchy.

How do I capture continuous terminal output from a background process for logging?

Continuous terminal output capture for logging is done using the capture-pane and pipe-pane commands. These verbs continuously pipe pane output to files for external ingestion and structured logging.

Do I need a running tmux server to manage detached background tasks?

Yes, managing detached background tasks requires a running tmux server pinned to a UNIX socket. This server maintains the session persistence required for long-running agents during detach and reattach cycles.

Can I respawn dead terminal panes for self-healing agent loops?

Yes, you can respawn dead terminal panes to create self-healing loops for long-lived agents. This orchestration ensures background tasks automatically restart if they crash or exit unexpectedly.

Why does my terminal agent lose its state when the window closes?

Terminal agents lose state when windows close because the process is tied to the terminal emulator. Moving the agent into a persistent tmux server prevents state loss during disconnects and crashes.