swarm-shutdown

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.

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.

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.

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.

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.