home / skills / microck / ordinary-claude-skills / superpowers-lab

superpowers-lab skill

/skills_all/superpowers-lab

This skill helps you control interactive CLI tools via tmux detached sessions, sending input and capturing output programmatically.

This is most likely a fork of the using-tmux-for-interactive-commands skill from obra
npx playbooks add skill microck/ordinary-claude-skills --skill superpowers-lab

Review the files below or copy the command above to add this skill to your agents.

Files (7)
SKILL.md
1.6 KB
---
name: using-tmux-for-interactive-commands
description: Use when you need to run interactive CLI tools (vim, git rebase -i, Python REPL, etc.) that require real-time input/output - provides tmux-based approach for controlling interactive sessions through detached sessions and send-keys
---

# Using tmux for Interactive Commands

## Overview

Interactive CLI tools (vim, interactive git rebase, REPLs, etc.) cannot be controlled through standard bash because they require a real terminal. tmux provides detached sessions that can be controlled programmatically via `send-keys` and `capture-pane`.

## When to Use

**Use tmux when:**
- Running vim, nano, or other text editors programmatically
- Controlling interactive REPLs (Python, Node, etc.)
- Handling interactive git commands (`git rebase -i`, `git add -p`)
- Working with full-screen terminal apps (htop, etc.)
- Commands that require terminal control codes or readline

**Don't use for:**
- Simple non-interactive commands (use regular Bash tool)
- Commands that accept input via stdin redirection
- One-shot commands that don't need interaction

## Quick Reference

| Task | Command |
|------|---------|
| Start session | `tmux new-session -d -s <name> <command>` |
| Send input | `tmux send-keys -t <name> 'text' Enter` |
| Capture output | `tmux capture-pane -t <name> -p` |
| Stop session | `tmux kill-session -t <name>` |
| List sessions | `tmux list-sessions` |

## Core Pattern

### Before (Won't Work)
```bash
# This hangs because vim expects interactive terminal
bash -c "vim file.txt"
```

### After (Works)
```bash
# Create detached tmux session
tmux new-session -d -s edit_session vim file.txt

# Send commands (Enter, Escape are tmux key names)
tmux send-keys -t edit_session 'i' 'Hello World' Escape ':wq' Enter

# Capture what's on screen
tmux capture-pane -t edit_session -p

# Clean up
tmux kill-session -t edit_session
```

## Implementation

### Basic Workflow

1. **Create detached session** with the interactive command
2. **Wait briefly** for initialization (100-500ms depending on command)
3. **Send input** using `send-keys` (can send special keys like Enter, Escape)
4. **Capture output** using `capture-pane -p` to see current screen state
5. **Repeat** steps 3-4 as needed
6. **Terminate** session when done

### Special Keys

Common tmux key names:
- `Enter` - Return/newline
- `Escape` - ESC key
- `C-c` - Ctrl+C
- `C-x` - Ctrl+X
- `Up`, `Down`, `Left`, `Right` - Arrow keys
- `Space` - Space bar
- `BSpace` - Backspace

### Working Directory

Specify working directory when creating session:
```bash
tmux new-session -d -s git_session -c /path/to/repo git rebase -i HEAD~3
```

### Helper Wrapper

For easier use, see `/home/jesse/git/interactive-command/tmux-wrapper.sh`:
```bash
# Start session
/path/to/tmux-wrapper.sh start <session-name> <command> [args...]

# Send input
/path/to/tmux-wrapper.sh send <session-name> 'text' Enter

# Capture current state
/path/to/tmux-wrapper.sh capture <session-name>

# Stop
/path/to/tmux-wrapper.sh stop <session-name>
```

## Common Patterns

### Python REPL
```bash
tmux new-session -d -s python python3 -i
tmux send-keys -t python 'import math' Enter
tmux send-keys -t python 'print(math.pi)' Enter
tmux capture-pane -t python -p  # See output
tmux kill-session -t python
```

### Vim Editing
```bash
tmux new-session -d -s vim vim /tmp/file.txt
sleep 0.3  # Wait for vim to start
tmux send-keys -t vim 'i' 'New content' Escape ':wq' Enter
# File is now saved
```

### Interactive Git Rebase
```bash
tmux new-session -d -s rebase -c /repo/path git rebase -i HEAD~3
sleep 0.5
tmux capture-pane -t rebase -p  # See rebase editor
# Send commands to modify rebase instructions
tmux send-keys -t rebase 'Down' 'Home' 'squash' Escape
tmux send-keys -t rebase ':wq' Enter
```

## Common Mistakes

### Not Waiting After Session Start
**Problem:** Capturing immediately after `new-session` shows blank screen

**Fix:** Add brief sleep (100-500ms) before first capture
```bash
tmux new-session -d -s sess command
sleep 0.3  # Let command initialize
tmux capture-pane -t sess -p
```

### Forgetting Enter Key
**Problem:** Commands typed but not executed

**Fix:** Explicitly send Enter
```bash
tmux send-keys -t sess 'print("hello")' Enter  # Note: Enter is separate argument
```

### Using Wrong Key Names
**Problem:** `tmux send-keys -t sess '\n'` doesn't work

**Fix:** Use tmux key names: `Enter`, not `\n`
```bash
tmux send-keys -t sess 'text' Enter  # ✓
tmux send-keys -t sess 'text\n'      # ✗
```

### Not Cleaning Up Sessions
**Problem:** Orphaned tmux sessions accumulate

**Fix:** Always kill sessions when done
```bash
tmux kill-session -t session_name
# Or check for existing: tmux has-session -t name 2>/dev/null
```

## Real-World Impact

- Enables programmatic control of vim/nano for file editing
- Allows automation of interactive git workflows (rebase, add -p)
- Makes REPL-based testing/debugging possible
- Unblocks any tool that requires terminal interaction
- No need to build custom PTY management - tmux handles it all

Overview

This skill shows how to use tmux to run and control interactive CLI tools programmatically. It provides a simple, repeatable pattern using detached tmux sessions, send-keys, and capture-pane to drive editors, REPLs, and full-screen terminal apps. The goal is reliable automation of interactions that require a real terminal.

How this skill works

Create a detached tmux session that runs the interactive command, wait briefly for initialization, and then drive the session with tmux send-keys to emit keystrokes (including special keys like Enter and Escape). Use tmux capture-pane to read the current screen contents, and kill the session when finished. This avoids building custom PTY handling by leveraging tmux’s terminal emulation.

When to use it

  • Automating interactive editors (vim, nano) where you must send keystrokes to edit and save files
  • Controlling REPLs (Python, Node) for scripted evaluations and stateful tests
  • Automating interactive git flows (git rebase -i, git add -p) that open an editor
  • Running full-screen tools (htop, ncurses apps) that require terminal control
  • Any command that depends on terminal control codes or readline behavior

Best practices

  • Start a detached session with a descriptive name and optional working directory (-c) so context is clear
  • Sleep briefly (100–500ms) after starting the session to let the process initialize before sending keys
  • Use tmux key names (Enter, Escape, C-c, Up, Down) rather than escape sequences like '\n'
  • Capture the pane after key sequences to verify state and output before proceeding
  • Always kill or check for existing sessions to avoid orphaned tmux sessions

Example use cases

  • Programmatically open vim in a detached session, insert content, save, and exit to modify files without TTY hacks
  • Drive a Python REPL to import modules, run test expressions, and capture printed output for assertions
  • Automate an interactive git rebase by editing the rebase todo, saving, and continuing
  • Script interactions with a full-screen diagnostic tool to capture its output for logging
  • Wrap common operations in a small wrapper script (start/send/capture/stop) for repeatable automation

FAQ

Why use tmux instead of plain bash with stdin redirection?

Plain stdin redirection often fails for apps that need a real terminal (full-screen apps, editors, readline). tmux provides a proper terminal environment and lets you send actual keystrokes.

How do I ensure commands actually run after send-keys?

Send special keys like Enter as separate arguments and capture the pane after sending keys. Add a short sleep when needed to allow the app to react.