run-long-running-processes-in-tmux

This skill manages long-running processes in detached tmux sessions, allowing you to start commands like local development servers in the background. It handles session creation, verification, and command injection so processes continue running after you close your terminal.

This skill provides output capture functionality for background processes running inside tmux sessions. You can retrieve the terminal output generated by the detached session for logging or analysis without needing to reattach to the terminal.

The best way to keep a local development server running after closing the terminal is using detached execution via tmux. This skill starts your server in a background session that persists independently of your active terminal connection.

Yes, you need tmux installed and configured on your system to manage background processes with this skill. It relies entirely on tmux's session management capabilities to handle detached execution and command injection.

Yes, you can send commands to a running background process through this skill's command injection feature. It supports sending new commands into existing detached tmux sessions for remote interaction with your server processes or automated tasks.

You manage the lifecycle of background processes in tmux by using this skill to create, verify, and kill sessions. It provides full session management capabilities to monitor, interact with, and cleanly clean up long-running commands.