skill-system-tmux

To prevent long-running shell commands from timing out, route them through tmux sessions for persistent execution. This approach keeps tasks alive in the background, ensuring they survive disconnects and continue running safely without terminal interference.

Use tmux session management instead of direct bash when commands risk timeouts, require persistence, or need interactive terminal access. A decision matrix evaluates command duration, interactivity, and persistence needs to determine the correct routing.

Manage multiple project tmux sessions by enforcing project-context session naming with oc- prefixes. This convention prevents naming conflicts, enables safe multi-project operation, and allows bulk cleanup to reclaim resources efficiently.

Yes, you can run persistent servers and background tasks in tmux that survive SSH disconnects. Routing remote executions through tmux ensures interactive sessions and long-running commands persist independently of the active SSH connection status.

The best way to clean up idle tmux sessions and reclaim system resources is through a bulk cleanup workflow. By enforcing oc- prefixes for session naming, you can safely identify and terminate orphaned background tasks across multiple projects.

Perform readiness checks on background servers running inside tmux by applying specific session patterns. These patterns monitor persistent servers routed through tmux, verifying task completion and service availability before proceeding with downstream executions.