terminal-detach-tmux-session

To detach from a tmux session without stopping background processes, the Skill disconnects the MCP from the active session, allowing the underlying workload to continue running uninterrupted after agent disconnection.

When you disconnect from a tmux session, your long-running workload continues to execute in the background. The Skill frees your terminal while ensuring the underlying processes remain active and uninterrupted.

Yes, you can detach using a specific session ID. The Skill validates that the provided session ID corresponds to an active tmux session before initiating the detach operation to ensure a successful disconnection.

You need to detach from a tmux session for background task management when you have long-running processes initiated with lifecycle tmux and require continued execution after leaving your terminal or disconnecting your agent.

Detaching from a tmux session does not terminate the processes inside. The Skill specifically disconnects the MCP from the tmux-backed session, ensuring the underlying workload continues running without interruption.