botoolagent-exit

Name: botoolagent-exit
Availability: InStock
Author: Botool-Dev-Team

Stop BotoolAgent agents, close the Viewer dev server, and clean up resources.

Updated Aug 27, 2026

Search Tags:#devops #agents #orchestration #tmux #graceful-shutdown #viewer #botoolagent

Ready to run

npx skills add https://github.com/Botool-Dev-Team/BotoolAgent --skill botoolagent-exit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: botoolagent-exit
Source: https://github.com/Botool-Dev-Team/BotoolAgent/tree/main/skills/BotoolAgent/Exit
Command: npx skills add https://github.com/Botool-Dev-Team/BotoolAgent --skill botoolagent-exit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gracefully shuts down the BotoolAgent stack: stopping running agents, closing the Viewer dev server, and cleaning up resources.

Core Features & Use Cases

Graceful shutdown of Stage 3/4 agents and the Viewer to prevent orphan processes.
Ordered shutdown sequence with environment detection and post-check verification.
Cleanup of residual tmux sessions and resource state to ensure clean restart.

Quick Start

Run botoolagent-exit to gracefully shut down BotoolAgent components and all running agents.

Frequently Asked Questions about botoolagent-exit

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

FAQPage Schema

How do I gracefully shut down running agents and the Viewer dev server?▼

To gracefully shut down running agents and the Viewer dev server, you need an ordered shutdown sequence that stops Stage 3/4 agents and closes resources safely to prevent orphan processes.

What is the best way to clean up residual tmux sessions after stopping dev agents?▼

Cleaning up residual tmux sessions requires terminating specific processes and clearing resource states during agent shutdown, ensuring a clean environment without leftover processes for your next restart.

How do I prevent orphan processes when stopping the BotoolAgent stack?▼

Preventing orphan processes during BotoolAgent stack shutdown involves executing an ordered termination sequence that explicitly stops Stage 3/4 agents, the Viewer, and any residual tmux sessions.

Do I need repository context and specific ports to terminate agents gracefully?▼

Yes, terminating agents gracefully requires repository context like the repo root, the viewer port, and explicit permission to terminate processes to perform a safe, ordered shutdown with verification.

Why does ordered shutdown with environment detection matter for dev orchestration?▼

Ordered shutdown with environment detection matters because it safely closes the Viewer dev server and running agents while verifying resource cleanup, which prevents state corruption and orphaned tmux sessions.