tmux-guide

Run long terminal tasks in background tmux sessions with agent- naming.

103|21|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/archibate/dotfiles-opencode --skill tmux-guide
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tmux-guide
Source: https://github.com/archibate/dotfiles-opencode/tree/main/tmux-guide
Command: npx skills add https://github.com/archibate/dotfiles-opencode --skill tmux-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents long-running or indefinite commands from blocking your terminal session by moving them into a managed tmux background session with consistent logging and cleanup rules.

Core Features & Use Cases

  • Background execution for long tasks: Run operations that take more than 2 minutes (installs, large test suites, training pipelines) without timing out.
  • Indefinite server/task handling: Keep services and port-forwarding running in the background reliably.
  • Failure-safe observability: Capture recent output (last 80 lines) without attaching, so you can debug while keeping your workflow non-intrusive.
  • Safety-focused session hygiene: Enforce the agent- session naming convention, avoid attaching, and avoid killing tmux server or unrelated sessions.

Quick Start

Use the tmux-guide skill before starting a long command (for example, installing dependencies or running many tests) so the command is executed inside a tmux session named with the agent- prefix and you can later capture the last 80 log lines if needed.

Frequently Asked Questions about tmux-guide

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

FAQPage Schema
How do I run long-running commands in the background without blocking the terminal?▼

To run long-running commands in the background without blocking the terminal, execute them inside a managed tmux session. This prevents operations like package installations or large test suites from timing out or freezing your current terminal window.

How can I check the debug logs of a background task without attaching to the tmux session?▼

You can check debug logs without attaching by using the tmux capture-pane command. This captures the last 80 lines of recent output directly from the background session, ensuring your workflow remains non-intrusive while debugging.

What is the best way to manage indefinite web servers or port forwarding safely?▼

The best way to manage indefinite web servers or port forwarding safely is to run them in a background tmux session. This approach enforces consistent logging and applies safe session hygiene to keep services running reliably.

How do I safely clean up tmux sessions after a model training or dataset pipeline finishes?▼

Safely clean up tmux sessions after model training or dataset pipelines by killing only the specific agent- prefixed sessions. This targeted cleanup approach ensures you avoid killing the tmux server or unrelated active sessions.

When should I use tmux for session management instead of running commands directly?▼

You should use tmux for session management when executing commands that take more than two minutes, such as extensive test runs or package installations. It prevents timeouts and ensures failure-safe observability for background tasks.