swarm-shutdown

Shut down a swarm team by broadcasting messages, confirming checkpoints, and terminating tmux sessions.

Updated Apr 10, 2026

Search Tags:#automation #orchestration #tmux #swarm #checkpoint #containers #shutdown

Ready to run

npx skills add https://github.com/stevengonsalvez/nanoclaw-standalone --skill swarm-shutdown

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: swarm-shutdown
Source: https://github.com/stevengonsalvez/nanoclaw-standalone/tree/main/container/skills/swarm-shutdown
Command: npx skills add https://github.com/stevengonsalvez/nanoclaw-standalone --skill swarm-shutdown

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gracefully shuts down a swarm team to ensure all agents are notified, checkpoints are captured, and resources are cleaned up in a safe, auditable manner.

Core Features & Use Cases

Graceful shutdown workflow: broadcasts shutdown intent to all agents, waits for checkpoints, and updates team state to reflect shutdown.
Forceful fallback: supports immediate termination when a graceful shutdown is not possible.
Auditable cleanup: terminates sessions and preserves final team data for archiving.

Quick Start

To shut down a swarm, run the CLI command with the team identifier and the optional --force flag.

Frequently Asked Questions about swarm-shutdown

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

FAQPage Schema

How do I gracefully shut down a swarm team without losing agent checkpoints?▼

To gracefully shut down a swarm team, you need a workflow that broadcasts shutdown intent to all agents, waits for their checkpoints to be captured, terminates tmux sessions, and updates the team state. This ensures safe, auditable cleanup during operational pauses or maintenance.

What is the best way to terminate tmux sessions for a swarm during an emergency?▼

The best way to handle an emergency swarm shutdown is using a forceful fallback option. This immediately terminates tmux sessions and agents when a graceful shutdown is not possible, bypassing the checkpoint waiting period to ensure rapid resource cleanup.

Can I force an immediate swarm shutdown if agents are unresponsive?▼

Yes, you can force an immediate swarm shutdown if agents are unresponsive. Using a forceful fallback flag bypasses the graceful notification and checkpoint confirmation workflow, allowing you to instantly terminate tmux sessions and clean up resources.

Does shutting down a swarm team preserve the final team state for auditing?▼

Yes, shutting down a swarm team preserves the final team data for archiving. The workflow updates the team state to reflect the shutdown and terminates active sessions while keeping the final data intact for safe, auditable review.

When should I use a forceful shutdown instead of a graceful swarm termination?▼

You should use a forceful shutdown instead of a graceful swarm termination during emergencies or when agents become unresponsive. If waiting for agent checkpoints is not possible, the forceful fallback immediately terminates tmux sessions to secure the environment.