tmux
Manage tmux sessions for interactive background processes
What this skill does
## Overview
CLI tools for managing tmux sessions, enabling agents to run and interact with background processes like database connections (psql, mysql), REPLs, log tailing, and other interactive commands.
## Prerequisites
- [bun](https://bun.sh) runtime installed
- [tmux](https://github.com/tmux/tmux) installed (`brew install tmux` or `apt install tmux`)
## Commands
### List Sessions
List all active tmux sessions.
```bash
bun .opencode/skill/tmux/list-sessions.js [options]
```
**Options:**
- `--json` - Output as JSON
**Examples:**
```bash
bun .opencode/skill/tmux/list-sessions.js
bun .opencode/skill/tmux/list-sessions.js --json
```
---
### Create Session
Create a new tmux session for running background processes.
```bash
bun .opencode/skill/tmux/create-session.js <name> [options]
```
**Arguments:**
- `name` - Session name (required)
**Options:**
- `--command <cmd>` - Initial command to run in the session
- `--workdir <path>` - Working directory for the session
- `--window <name>` - Name for the initial window
- `--json` - Output as JSON
**Examples:**
```bash
# Create a session for psql
bun .opencode/skill/tmux/create-session.js db-session --command "psql -h localhost -U postgres mydb"
# Create a session for tailing logs
bun .opencode/skill/tmux/create-session.js logs --command "tail -f /var/log/app.log"
# Create a session in a specific directory
bun .opencode/skill/tmux/create-session.js dev --workdir ~/projects/myapp
```
---
### Send Command
Send a command to a tmux session (types the command and presses Enter).
```bash
bun .opencode/skill/tmux/send-command.js <session> <command> [options]
```
**Arguments:**
- `session` - Session name (or session:window or session:window.pane)
- `command` - Command to send
**Options:**
- `--no-enter` - Send keys without pressing Enter
- `--literal` - Send keys literally (no special key interpretation)
- `--json` - Output as JSON
**Examples:**
```bash
# Run a SQL query in a psql session
bun .opencode/skill/tmux/send-command.js db-session "SELECT * FROM users LIMIT 10;"
# Send Ctrl+C to interrupt a process
bun .opencode/skill/tmux/send-command.js logs "C-c" --no-enter
# Type text without executing
bun .opencode/skill/tmux/send-command.js dev "echo hello" --no-enter
```
---
### Capture Output
Capture and read the current output from a tmux session pane.
```bash
bun .opencode/skill/tmux/capture-output.js <session> [options]
```
**Arguments:**
- `session` - Session name (or session:window or session:window.pane)
**Options:**
- `--lines <n>` - Number of lines of scrollback to capture (default: 100)
- `--wait <pattern>` - Wait for output matching this pattern before capturing
- `--timeout <ms>` - Timeout for --wait in milliseconds (default: 30000)
- `--json` - Output as JSON
**Examples:**
```bash
# Capture recent output from a session
bun .opencode/skill/tmux/capture-output.js db-session
# Capture more scrollback history
bun .opencode/skill/tmux/capture-output.js logs --lines 500
# Wait for a specific prompt before capturing
bun .opencode/skill/tmux/capture-output.js db-session --wait "postgres=#" --timeout 5000
```
---
### Kill Session
Terminate a tmux session.
```bash
bun .opencode/skill/tmux/kill-session.js <name> [options]
```
**Arguments:**
- `name` - Session name to kill
**Options:**
- `--json` - Output as JSON
**Examples:**
```bash
bun .opencode/skill/tmux/kill-session.js db-session
```
---
## Common Workflows
### Database Session (psql)
```bash
# Create a psql session
bun .opencode/skill/tmux/create-session.js psql --command "psql -h localhost -U postgres mydb"
# Wait for connection, then run queries
bun .opencode/skill/tmux/capture-output.js psql --wait "postgres=#"
bun .opencode/skill/tmux/send-command.js psql "SELECT COUNT(*) FROM users;"
# Capture the query results
bun .opencode/skill/tmux/capture-output.js psql --lines 50
# Clean up when done
bun .opencode/skill/tmux/kill-session.js psql
```
### Log Monitoring
```bash
# Start tailing logs
bun .opencode/skill/tmux/create-session.js logs --command "tail -f /var/log/app.log"
# Check for errors periodically
bun .opencode/skill/tmux/capture-output.js logs --lines 200
# Stop monitoring
bun .opencode/skill/tmux/kill-session.js logs
```
### Interactive REPL (Python, Node, etc.)
```bash
# Start a Python REPL
bun .opencode/skill/tmux/create-session.js python --command "python3"
# Run Python commands
bun .opencode/skill/tmux/send-command.js python "import pandas as pd"
bun .opencode/skill/tmux/send-command.js python "df = pd.read_csv('data.csv')"
bun .opencode/skill/tmux/send-command.js python "df.describe()"
# Capture output
bun .opencode/skill/tmux/capture-output.js python
```
---
## Output Behavior
- Command output is displayed directly to the user in the terminal
- **Do not re-summarize or reformat output** - the user can already see it
- When capturing output, the raw terminal content is returned (may include ANSI codes)
- Use `--json` for structured output when parsing programmatically
## Notes
- Session names should be descriptive and unique (e.g., `psql-mydb`, `logs-app`)
- Target format: `session` or `session:window` or `session:window.pane`
- Special keys: `C-c` (Ctrl+C), `C-d` (Ctrl+D), `C-m` (Enter), `C-l` (clear)
- Sessions persist until explicitly killed or system restart
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.