tmux

Register and manage tmux sessions with a registry-backed workflow.

Updated Feb 14, 2026
One-click install
npx skills add https://github.com/Shakudo-io/opencode-skills --skill tmux-shakudo-io
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tmux
Source: https://github.com/Shakudo-io/opencode-skills/tree/main/tmux
Command: npx skills add https://github.com/Shakudo-io/opencode-skills --skill tmux-shakudo-io

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires tmux, jq, bc, grep, sed, awk, date, and includes scripts (resource) and references (resource) components.

What problem does it solve?

tmux sessions are powerful but managing them across multiple tools often requires repeating socket/target details and manual tracking. This Skill provides a registry-backed workflow to create, locate, monitor, and clean up tmux sessions, reducing boilerplate and enabling safer automation.

Core Features & Use Cases

  • Session registry: reference sessions by name instead of socket/target, enabling auto-detection and health-aware operations.
  • Lifecycle tools: create-session.sh, list-sessions.sh, cleanup-sessions.sh for bootstrapping, discovery, and cleanup.
  • Reliable interactions: safe-send.sh, wait-for-text.sh, and pane-health.sh for robust automated control of interactive programs (Python REPLs, gdb, git, shells).
  • Health and monitoring: pane-health.sh and time-based cleanup ensure stale or dead panes are handled gracefully.
  • Use cases: debugging, multi-session workflows, and automation of terminal-driven tasks.

Quick Start

Create a new tmux session with create-session.sh -n <name>, then drive commands with safe-send.sh.

Frequently Asked Questions about tmux

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

FAQPage Schema
How do I automate interactive shell sessions in tmux without repeating socket details?

Automating interactive shell sessions in tmux requires a session registry to track targets by name. This Skill provides a registry-backed workflow with scripts like create-session.sh and safe-send.sh, reducing boilerplate for terminal automation.

What is the best way to manage multiple tmux sessions for long-running tasks like Python REPLs or gdb?

Managing multiple tmux sessions for long-running tasks like Python REPLs or gdb requires lifecycle and health monitoring tools. This Skill uses pane-health.sh and cleanup-sessions.sh to monitor, track, and safely clean up stale or dead interactive panes.

How do I send commands safely to an interactive terminal inside an automated tmux workflow?

Sending commands safely to an interactive terminal in an automated tmux workflow requires checking pane health first. This Skill provides safe-send.sh and wait-for-text.sh to ensure robust, reliable command delivery to active sessions.

Can I use this tmux session registry to detect and clean up stale panes automatically?

Yes, you can use this tmux session registry to detect and clean up stale panes automatically. The Skill implements pane-health.sh for health checks and time-based cleanup-sessions.sh to gracefully handle dead or unresponsive interactive terminal panes.

Do I need jq and bc installed to run these tmux automation scripts?

Yes, running these tmux automation scripts requires dependencies like jq, bc, grep, sed, awk, and date to be installed. These tools support the session registry logic, health checks, and text processing within the automation workflow.

Why does my tmux automation break when sending commands to unresponsive panes?

Tmux automation breaks when sending commands to unresponsive panes because standard sending lacks health verification. This Skill solves it using pane-health.sh to check status before safe-send.sh delivers commands, ensuring robust automated control.