yato-cleanup

To safely terminate Yato agents and clean up tmux sessions, run the yato-cleanup skill. It systematically kills Yato agents, terminates tmux sessions, halts check-in daemons, and optionally deletes the workflow directory to prevent resource leaks.

The best way to prevent resource leaks when ending a Yato workflow is to execute a systematic cleanup process. This ensures all running agents, tmux sessions, and background check-in daemons are properly killed and marked as completed.

Yes, you can delete the workflow directory during Yato system termination. The cleanup process offers an optional argument to completely remove the workflow directory after successfully halting all agents and terminating active tmux sessions.

Yes, you need specific environment permissions for file operations and process management to halt check-in daemons and release Yato resources. The cleanup process assumes the environment is already configured with the necessary Yato dependencies.

Your Yato workflow status remains active because simply killing tmux sessions does not update the workflow state or halt check-in daemons. A dedicated cleanup process is required to mark the workflow as completed and ensure all components are terminated.