ssh-long-running-job

Automate long-running SSH commands in tmux sessions with progress monitoring.

6|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/Nightreaver/python-ssh-mcp --skill ssh-long-running-job
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ssh-long-running-job
Source: https://github.com/Nightreaver/python-ssh-mcp/tree/main/runbooks/ssh-long-running-job
Command: npx skills add https://github.com/Nightreaver/python-ssh-mcp --skill ssh-long-running-job

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the execution of long-running SSH commands, monitors their progress, and ensures they complete successfully, even if the MCP server restarts or the network blinks.

Core Features & Use Cases

  • Long-Running Command Execution: Run multi-hour commands in a detached tmux session.
  • Progress Monitoring: Continuously check on the job's status and progress.
  • Completion Verification: Ensure the command finishes and the outcome is as expected.
  • Use Case: Ideal for tasks like large file transfers, long-running backups, or complex data processing jobs that require sustained execution and reliable recovery from interruptions.

Quick Start

Use the ssh-long-running-job skill to execute a long-running command on a remote host, such as 'rsync -aP --partial --append-verify --log-file=/var/log/my-rsync.log /data/ user@dst01:/data/'.

Frequently Asked Questions about ssh-long-running-job

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

FAQPage Schema
How do I keep long-running SSH commands running after disconnecting?

Long-running SSH commands stay active after disconnection by executing them inside a detached tmux session, which maintains process state independently of the SSH connection and survives network interruptions.

Can I monitor the progress of a remote SSH command that takes hours to finish?

Monitoring progress for hours-long SSH commands is handled by continuously checking the job status within the tmux session, utilizing host-notes for state persistence to report updates even after an MCP server restart.

What is the best way to ensure a large remote backup or data transfer completes successfully?

Ensuring large remote backups complete successfully requires automated execution in a detached tmux session with continuous progress monitoring and completion verification, allowing reliable recovery from network issues or restarts.

Does executing long-running commands over SSH work if the MCP server restarts?

Executing long-running commands over SSH survives MCP server restarts because the process runs in a detached tmux session and uses host-notes for state persistence, allowing the monitoring to resume seamlessly.

Why does my long-running SSH command stop when the network drops?

Long-running SSH commands stop on network drops because they rely on the active SSH connection, but running them in a detached tmux session isolates the process from network blinks and ensures sustained execution.

Do I need tmux to automate multi-hour remote command execution?

Using tmux is required to automate multi-hour remote command execution because it provides the detached session necessary to keep the process running independently of the SSH connection and recover from interruptions.