resilient-executor

Automates long-running task persistence with tmux sessions, heartbeats, and checkpoints.

Updated Nov 22, 2025
One-click install
npx skills add https://github.com/Khamel83/oneshot --skill resilient-executor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resilient-executor
Source: https://github.com/Khamel83/oneshot/tree/main/archive/v9/skills/resilient-executor
Command: npx skills add https://github.com/Khamel83/oneshot --skill resilient-executor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables persistent execution of long-running tasks by running them inside a tmux-backed session that survives terminal disconnects and provides recovery data.

Core Features & Use Cases

  • Persistent sessions using tmux that survive SSH disconnects and terminal closes.
  • Heartbeat & checkpoints that log activity and allow resuming tasks from beads state.
  • Recovery workflows that guide reattachment and continuation after interruptions, including state synchronization.

Quick Start

Start a resilient session by running the oneshot-resilient.sh script to carry out a long-running task.

Frequently Asked Questions about resilient-executor

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

FAQPage Schema
How do I keep long-running tasks alive after an SSH disconnect?

You can keep long-running tasks alive after an SSH disconnect by running them inside a tmux-backed session that persists through terminal closures. The session maintains execution state independently of your active connection.

How does tmux session recovery work for background builds?

Tmux session recovery for background builds works by logging heartbeat activity and periodic checkpoints. This allows you to reattach to the session and resume the workflow from its last saved beads state.

Do I need tmux installed to use persistent session management?

Yes, you need tmux installed because the skill uses a tmux-backed session to automate persistence. It relies on tmux to isolate processes and survive terminal disconnects.

What is the best way to automate long-running tasks that survive terminal closes?

The best way to automate long-running tasks that survive terminal closes is using a script that initializes a tmux session with heartbeat logging and periodic checkpoints. This ensures resilient state management.

Can I resume autonomous builds from a checkpoint after an interruption?

Yes, you can resume autonomous builds after an interruption by recovering from beads-based state. The checkpoint and heartbeat data guide state synchronization and task continuation.